Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50945
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <4D00ABFE.5070403@hristov.com>
References: <4D00ABFE.5070403@hristov.com>
Date: Thu, 9 Dec 2010 20:40:06 +0800
Message-ID: <AANLkTi=5gs-_QGJVRmH0o+Cfu-pGYHymEOfRpCDr_wL8@mail.gmail.com>
To: Andrey Hristov <php@hristov.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST,
 $_GET, $_POST read-only
From: aharvey@php.net (Adam Harvey)

On 9 December 2010 18:14, Andrey Hristov <php@hristov.com> wrote:
> the topic says most of it. What do you think about deprecating the global
> keyword and $GLOBALS with it? Together with this making $_REQUEST, $_GET and
> $_POST read-only as they should be used only to read-only anyway.

-1 here. No question that if you were developing a new language with
similar design goals to PHP (but learning from the missteps), you'd
probably make the superglobal analogues read only and skip the idea of
$GLOBALS altogether, but there's just too much code out there that
relies on these "features" working.

Adam