RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only
| From: | James Butler | Date: | Thu, 09 Dec 2010 10:31:39 +0000 |
| Subject: | RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50926@lists.php.net to get a copy of this message | ||
-----Original Message-----
From: Andrey Hristov [mailto:php@hristov.com]
>James Butler wrote:
>> +1 million because GLOBAL scope is horrid (generally) and is thoroughly abused
>> -1 million because it will be the most horrific BC break since time began and I imagine it
>> will break so much code that is currently in the wild...
>how hard it will be to grep for "global" and $GLOBALS?
Not hard for you or I but what about the beginners out there, will they know how to find them or
work around the use of globals?
>> In short I like it but I'm not sure how it would ever get implemented without breaking
>> stuff... (this is where the clever core developers can propose some easy method I can't think
>> of right now)
>INI variable, like register_globals
Sorry, I wasn't being very clear there, what I really meant to say was will there be the will
to remove it considering the effects.
I suppose INI is enough to allow it to be easily changed, but would it ever become a default setting
of off, rather than something that can be optionally off?