Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107282
MIME-Version: 1.0
References: <CAP=w73Xe+x92W7K8dVXjH+e+shk8+Ui8J5v7T94X=+qdTJoQsg@mail.gmail.com>
 <CAF+90c82NSW+Mr483ycFnjNRDcEW0cSnwoM1r4OzGdMtPCuNYA@mail.gmail.com>
 <CAP=w73Uevg9visVP1k+w-oqySMoH8420Y2jHjsh+h1dyGmLKZQ@mail.gmail.com>
 <CAF+90c-S4k=p4c_xJc-+1pFXSRUF4LkbruN9QRoa2+6VkrVSqQ@mail.gmail.com>
 <CAP=w73W8HUdc39Afaxggz4D1Vbb=f=OaQ57To9P+=4oakvzcYA@mail.gmail.com> <CAJHtznyf4mMopxW+x0UOO+hN6si++E-YgjgUqrJncxDjdPZZbA@mail.gmail.com>
In-Reply-To: <CAJHtznyf4mMopxW+x0UOO+hN6si++E-YgjgUqrJncxDjdPZZbA@mail.gmail.com>
Date: Sat, 21 Sep 2019 22:18:10 +0700
Message-ID: <CAP=w73WdRSTnPr0OC0b41Af+FHyqLu5xNFZe+tD+XanopE=0_g@mail.gmail.com>
To: Zeev Suraski <zeev@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000076cc34059311b250"
Subject: Re: [PHP-DEV] Question about `global` variable declaration
From: webdevxp.com@gmail.com (Kosit Supanyo)

--00000000000076cc34059311b250
Content-Type: text/plain; charset="UTF-8"

>
> Unlike var, public, static and others - 'global' is not a declaration of
> class structure, but a way to access global variables.


I know it is not and I think almost everyone knows that. As I said, I came
up with this by comparing to other declarations syntactically not
functionally, it is inconsistent in that way. I don't know how many PHP
developers out there know `global` can take variable variables but I my
guess is, very very little because there's no information about this
behavior of `global` in PHP manual
https://www.php.net/manual/en/language.variables.scope.php and I'd never
seen those forms of `global` in any projects/articles before.

Cheers

On Sat, Sep 21, 2019 at 9:26 PM Zeev Suraski <zeev@php.net> wrote:

> On Sat, Sep 21, 2019 at 3:09 PM Kosit Supanyo <webdevxp.com@gmail.com>
> wrote:
>
>> I understand your point but inconsistency in my sense is syntactical By
>> comparing to other declaration syntax like `var`, `static`, 'public` an
>> others. They allow only T_VARIABLE but `global` is different. And there's
>> another way to archive the same goal through `$GLOBALS`, that's why I see
>> it as inconsistency.
>>
>
> Even though we're dealing with archeology here - this really isn't an
> inconsistency but intended behavior.
> Unlike var, public, static and others - 'global' is not a declaration of
> class structure, but a way to access global variables.  In the same way it
> sometimes makes sense to access variables indirectly ($$foo), it may
> sometimes make sense to access global variables indirectly (global $$foo).
> It allows for both creation and access of global variables.  It doesn't
> sound very useful or practical to provide that ability for the creation of
> dynamic class properties, which is why it's not available for
> var/public/static/etc.
>
> Zeev
>

--00000000000076cc34059311b250--