Conversation

Notices

1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Wednesday, 04-Oct-2017 22:25:37 EDT lnxw48a1
   @natecull I believe !tcltk dates back to the early #1980s, so that explains some of the legacy cruft. (I don't see much use for octals any more, but maybe it is time for a oX [small-oh eks] prefix if they are still needed. 0X [zero eks], of course, should be reserved for hexadecimals, which are still useful.)
   1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Wednesday, 04-Oct-2017 23:17:03 EDT lnxw48a1

      in reply to
      History of !tcltk http://www.tcl.tk/about/history.html
   2. Vertigo (vertigo@mastodon.social)'s status on Thursday, 05-Oct-2017 02:07:57 EDT Vertigo

      in reply to

      @lnxw48a1 @natecull We should stop trying to reinvent the wheel all the time. IBM solved this with their mainframe assembly and PL/I syntax using annotated strings (e.g., '3C'X versus '00111100'B). Smalltalk (IIRC) has a similar generic approach (16r3C and 2r00111100), though I admit I prefer IBM's notation simply because it seems more open-ended.