Re: Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only
| From: | Andrey Hristov | Date: | Thu, 09 Dec 2010 16:55:50 +0000 |
| Subject: | Re: Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50960@lists.php.net to get a copy of this message | ||
Alain Williams wrote:
On Thu, Dec 09, 2010 at 05:40:09PM +0100, Reindl Harald wrote:AndreyAm 09.12.2010 17:19, schrieb Andrey Hristov:+1one day you might have to support globalized applications and I am sure you will feel very enlightened to fix them :)This is my problem and not yours There are thousands of scripts that are not big applications and running well, are secure and clear designed and simply working since yearsSo why in the world would you like to kill them braindead without any valid reason, and "i do not like something" is not a valid reason because nobody forces you to use such things in your scriptsNot using (a small number of) globals needs either: * functions that take everthing that they need in arguments. I tried that 30 years ago and never did it again, functions with 15 arguments are unweildy &* hard to maintain. * Use OO. That means a whole step up in design, not always justified in small scripts. OO is not always the answer. If all your functions take 15 params I am worried that your program design is flawed, sorry.