Short answer is no, but better question would be why are you making so many globals. Most best practices indicate you should have as few globals as possible (perhaps using a single global object or array instead) to cut down on data corruption issues. The problem w/globals is that as your system grows you don't know who is accessing the global and/or messing it up. This is why most systems shield globals and provide an object with methods that restrict access (or even audit access) to make the system cleaner to maintain.
Dave
===========================================
http://badblue.com/helpphp.htm
Free small footprint web server for Windows
PHP, P2P file-sharing, transcoding and more
