This assumes there is never a good reason for a super global which makes me wonder why PHP has super globals at all then? What if, because I use
There is a good reason, and exactly for things that PHP has as superglobals. Because these variables - system variables - are unique and well-known. We have to balance between cases where some dangerous functionality can be useful, and cases where some useful functionality can be dangerous. For superglobals, user-defined ones have danger far outweight the usefulness, and we have a number of good and working alternatives, so the case seems to be clear.
All this forcefulness of writing pristine code from the people that teach people that it's okay to inline their HTML, Javascript, CSS, SQL, and who knows what else into their PHP? Talk about a recipe for disaster. Oh well, at least you didn't refuse to add a switch statement like Python.
We do not (at least I do not :) refuse things just because we like to be purists and torture developers. There's a good reason for that, and I believe it was explained in the emails in this thread.
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
