Jens Rieks wrote:
Because global variables in tcl are different than global state
internal to my interpreter, and it would probably be sporting of me to
only expose the variables defined in the language, rather than those
used internally by the bytecode - so, if global opcodes are the way to
store global language variables, then I need a way to hide my private
data.

You can also use another namespace:
store_global "TCL::InternalData", "globals", the_hash
...
find_global the_hash, "TCL::InternalData", "globals"
Using special ASCII characters in the name might also avoid accidental access of "your globals".
...or you could document it as a feature, enabling enhanced introspection versus "standard" TCL.

("It's not a bug, it's a feature!")

-=- James Mastros

Reply via email to