> In a project with as many globals as we have, it's kinda handy to > know at a glance whether a member function is accessing a data > member or a global.
Add a globals-in-namespaces rule, or a ::global syntax, and you have even more overkill. IMHO we should make it easy to implement a clean design, and hard to implement a poor one. Use the extra syntax on the cases we want to discourage (cross-module references, non-namespace-globals, etc) and leave the desirable designs (well-contained code, modularization) with the simpler syntax.
