Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50951
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.45 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=lUoDLanXxLjjsT00QOpE97BKEljybTK/8sti4j1nPQov7R5PCrb+gAZNTO46dcvcaQ
         EqFRkSdM2s3wOr2JyO+CfxxrDOcWYCBOvKB/lD0AK1OvLXGK9zjGO3ni1CBBQt1xtlV1
         K4HaeHW63uKpUKAeCFh8qxzcPU54zYLUFfKj4=
Message-ID: <4D00FFDD.7040107@gmail.com>
Date: Thu, 09 Dec 2010 17:12:13 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Andrey Hristov <php@hristov.com>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <4D00ABFE.5070403@hristov.com> <AANLkTinDpmr2++Ys50tcbEPczrbz7eZKzXvvT+LG1CcD@mail.gmail.com> <4D00C86D.70208@hristov.com>
In-Reply-To: <4D00C86D.70208@hristov.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST,
 $_GET, $_POST read-only
From: keisial@gmail.com ("=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=")

Andrey Hristov wrote:
> I am not against global variables, I'm against usage of $GLOBALS and
> "global".

So how do you support global variables by banning the two ways they can
be accessed?

-1



>>  From a Framework point of view, they should save all of the
>> (super)global variables from the global scope, because the frameworks
>> doesn't use/run code in the global scope except the bootstrap, so
>> they couldn't access that either, but they won't know what the
>> developer who uses the framework want's to access from the global scope.
>> And what about global constants? They are also screwing up the
>> Dependency Injection, and the static functions/properties, and the Â
>> singletons also. Â Should we ban those?
>
> no, you got me wrong. I will repeat - global variables won't cease to
> exist, but $GLOBALS and "global" as means to access them should be
> removed. If a function needs data it should get it passed to it.

That's like trying to forbid TSRMLS_FETCH() in php source saying "just
use TSRMLS_DC instead". Sure it is a nice goal but
a) That's not always feasible [without rewriting an insane amount of code]
b) It's not a restriction that should be imposed by the language.