I don't understand, people keep telling me this can cause problems so it's trash. Really? Functions and variables can cause problems too. Not to mention user input. Programming is not easy, but the more flexible it is the better. I think it's up to the programmer to keep track of his variables, rather than us limiting his functionality, just incase he makes a mistake.
Any programmer can write bad code and it won't work. If he uses superglobals he should understand that he needs to document them, it's that simple. If that's too difficult, don't create a superglobal then, great. And if this isn't good enough, fine. Require an underscore for superglobals to differentiate them even more. I'll write the code myself, no problem. On Sat, 2007-11-17 at 01:30 -0500, Robert Cummings wrote: > On Sat, 2007-11-17 at 01:21 -0500, Sam Barrow wrote: > > True. What if we created a php.ini directive that defaulted to off that > > would determine the ability to declare superglobals, > > "allow_superglobals" or something. > > Does your code live in a bubble? Allowance of of arbitrary super global > definitions would open a can of local variable clobbering worms. > > A php.ini directive won't make this reality any more palatable. > > Cheers, > Rob. > -- > ........................................................... > SwarmBuy.com - http://www.swarmbuy.com > > Leveraging the buying power of the masses! > ........................................................... > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
