The explicit tail calls look pretty neat. All languages should include this, or something like it, I think; tail calls come in handy for all sorts of things. Making it explicit sidesteps complaints about how it will impede debugging, and ensures programmers will definitely get it where they want/expect.<p>I think this would be a chance to rehabilitate the much-maligned GOTO keyword. But "tailcall" is probably just as good.
Is this the programming language that works without a lexer/parser and a grammar? Why aren't there more programming languages written this way? Seems easier to implement.
that's an impressive set of changes for a minor release! :o)<p>is there a paper that describes the underlying implementation (with the new stackless stuff)?
The TIP#257[1] (Tcl Improvement Proposal) explains how rich and thought-out the TclOO component is. Endless possibilities.
It's a nice read to learn more about OO-concepts like filters, mixins and meta-classes.<p>Some might ask how TclOO compares to iTcl's. For one the performance is in another league.[2](Version 0.3)<p>[1] <a href="http://www.tcl.tk/cgi-bin/tct/tip/257" rel="nofollow">http://www.tcl.tk/cgi-bin/tct/tip/257</a><p>[2] <a href="http://wiki.tcl.tk/18152#pagetoc16f40cc9" rel="nofollow">http://wiki.tcl.tk/18152#pagetoc16f40cc9</a>
I lurk on the core list so I got to watch discussions relating to 8.6 stuff. It was pretty cool. There was a lot of thought about what went in and what needed to to be tweaked.