>> 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 ;-)

I also use properties when needed, but if in a loop, I always grab the property to a memvar and always use the mdot to get the least confusion of the compiler and the most speed possible. If a simple rule can be had to give both of those, then take it.