In short: Globals can be bad, but not always, it depends on the situation PHP is about getting stuff done... It gives developers the rope, if they want to hang themselves thats up to them.
If PHP was designed tomorrow, it might not have globals. but it does, they are in use and removing them because some people abuse them is not a good enough reason considering the damage it will cause to lots of perfectly ok designed and thought up code. If it aint broken, don't fix it! Globals aren't that broken, and if you use a framework its not a issue anyway.. This is turning into a GOTO-esque argument... -----Original Message----- From: Pierre Joye [mailto:pierre....@gmail.com] Sent: 09 December 2010 16:59 To: Andrey Hristov Cc: PHP Internals List Subject: Re: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only On Thu, Dec 9, 2010 at 5:58 PM, Pierre Joye <pierre....@gmail.com> wrote: > On Thu, Dec 9, 2010 at 5:55 PM, Andrey Hristov <p...@hristov.com> wrote: > >> If all your functions take 15 params I am worried that your program design >> is flawed, sorry. > > but that's a reason +not :) -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
