On 13 Apr 2006, at 20:15, Peter MacDonald wrote:
> 
> > I think in this case ".0" should *not* be recognized as a number.   
> > This
> > is not an unreasonable restriction for expressions, IMO.
> 
>  The same breakage can result from [proc 0 ...] etc.
> 
>  A more real-world example of this tip in use is something like:
> 
>    set x [$a+9]
> 
>  Does placing restrictions on the value of $a make sense?

proc 0 will break things, as specified in the TIP. In a way, this is  
intentional as it offers backwards compatibility and also is  
consistent with all other commands. However, I have never seen code  
which does [proc 0]. Even if such code exists, it obviously is not  
expecting there to be functionality like TIP 266 in the language.  
This argument could be used for any code which replaces a core  
command of the language. You can always break things if you want.  
That's how Tcl works.

            /  http://www.fishpool.com/~setok/



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core