Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50975
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.193 as permitted sender)
Message-ID: <4D013448.9060601@sugarcrm.com>
Date: Thu, 09 Dec 2010 11:55:52 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Andrey Hristov <php@hristov.com>
CC: PHP Internals List <internals@lists.php.net>
References: <4D00ABFE.5070403@hristov.com>
In-Reply-To: <4D00ABFE.5070403@hristov.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST,
 $_GET, $_POST read-only
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> the topic says most of it. What do you think about deprecating the
> global keyword and $GLOBALS with it? Together with this making

No, I think it's a bad idea. I know over-using globals is bad, but they 
still have their uses and huge amount of apps is using them one way or 
another.

> $_REQUEST, $_GET and $_POST read-only as they should be used only to
> read-only anyway.

This would probably be bad for tests on many applications, and quite big 
BC break.

> The reason for global + GLOBALS is that these are abused and which leads
> to spaghetti programs, when used by unexperienced users. Also they have
> impact on side effects from functions that don't only rely their parameters.

I don't believe you can B&D users into a good code. Java has tons of 
awful code.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227