Hi,
>  As a matter of principle, I don't want to have state that the object
>  can't inspect on itself; I think that that would be un-Tclish. That in
>  turn means that I'm inclined to say that if two classes use the same
>  variable name, they get the same variable (which greatly reduces the
>  complexity of the implementation). 
I'm quite happy with this approach, so long as everyone understands that 
this is the approach ;) 
It would probably be worth adding a note to the documentation (of 
object::variable) that variables intended to be private should be named 
using a unique prefix (like the class name) to prevent conflict.

Regards,
Trevor


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core