From: Jeff H. <jeffh@ActiveState.com> - 2003-08-06 15:10:19
|
Jacob Levy wrote: > * Do we use up the remaining free syntax for a solution that (to Peter and > several others) appears more intuitive than a command. > * --OR-- Do we save the syntax for later uses because there might be cases > where it won't be possible to do something easily with a command. > > My $0.02 is to save the syntax up for later, especially since its possible In over 10 years working with Tcl, I cannot think of another deficiency in the basic Tcl syntax that should otherwise occupy that syntax. If that is the case for others, why save it? There is nothing to save for. That said, I would like to see us consider possible new syntax for Tcl9 to improve the usability of lists and/or new data structures. I still think that would change the RHS of a token, where this {} on the LHS is still fairly unique in purpose. > If forced to choose between {} and {expand} I'd choose {}. Per JO's > invocation of the "Huffman encoding rule", the shortest sequence (in this > case {}) should be the least specific one. If you choose {expand} what is > the meaning of {} ?? I have to agree with that. I would vote for nothing over {expand}. -- Jeff Hobbs The Tcl Guy Senior Developer http://www.ActiveState.com/ Tcl Support and Productivity Solutions |