>> Thus, I only have to remember two things in order to avoid ambiguities: don't use PUBLIC vars (or use them sparsely), and always mdot.
>
>My general rule is, if there is a need for a global memory slot, put it into one of up to about 2 handful global objects I sometimes hang onto the app, _screen or plain memory. Exceptions of this rule (most of the time speed relevant counters/timers, where I like to minimize Heisenberg effects) are prefixed with Hungarian notation and get painfully long variable names, so you always ctrl-c the name when coding and give yourself a mental prod ;-)

Agreed. I, personally, don't use global vars, and those that warrant a global scope belong as members of the _screen object. Actually, _SCREEN.App is a first class citizen in my programs:)
*