News for hackers. Stuff that matters.
Re:The return of the Tcl browser plugin by kragen on Tuesday October 06, 2015 @06:34PM (#10342898)
It pretty much is cemented into the form it had at that time. My 1997 code runs in current Tcl/Tk, although I had at some point broken it by adding a #comment without a semicolon before it, but that was never valid. I think Tcl introduced some incompatibilities around 1992 or 1993, since the old icb client I used, which embedded an early version of Tcl from around that time, had some incompatibilities with scripts written in Tcl 4.

1997 is probably pretty close to the last time I worked with Tcl.

Tcl lists and arrays (dictionaries) are great, but arrays aren't first-class; you can't pass them as arguments or return them from expressions, only store them in variables. I'd argue that TclOO objects aren't first-class either: you don't have to explicitly destroy strings or lists (which are strings!) or even arrays when you're done with them, but you do have to explicitly destroy TclOO objects, just like Tk widgets.

I don't mean to imply that the object-graph memory model used by Lisp, Python, Perl 5, Java, ML, and Ruby has no disadvantages compared to the flatter memory model used by Tcl, Perl 4, and awk. But usually, for the things I do in low-performance interpreters, the disadvantages of the object-graph memory model are less compelling than the advantages. (I have some draft notes on this at http://canonical.org/~kragen/memory-models, if you're interested.)

I hope you enjoy the slide rule :)

Re:The return of the Tcl browser plugin by bch on Tuesday October 06, 2015 @08:01PM (#10343291)
> Tcl lists and arrays (dictionaries) are great, but arrays aren't first-class...

I forgot about arrays, tbh. I personally don't like the "feel" of them. The dictionaries I was referring to are these guys: https://www.tcl.tk/man/tcl/TclCmd/dict.htm

Nice to hear your thoughts on the matter, though.

Cheers.