Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118977
MIME-Version: 1.0
References: <CAPyj-LDUD7PZ9Bcpmsc0B_WjdnOSBPhdwfJsseB6n8PesPbzhw@mail.gmail.com>
In-Reply-To: <CAPyj-LDUD7PZ9Bcpmsc0B_WjdnOSBPhdwfJsseB6n8PesPbzhw@mail.gmail.com>
Date: Sun, 6 Nov 2022 21:06:48 +0100
Message-ID: <CAF+90c8kcvP9KE-0nhs7Ax1P4Za-ST8ikQysfM7_Xw-C8Ufvhw@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c3a8cd05ecd2d9de"
Subject: Re: [PHP-DEV] [RFC][Dynamic class constant fetch]
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000c3a8cd05ecd2d9de
Content-Type: text/plain; charset="UTF-8"

On Fri, Nov 4, 2022 at 3:26 PM Ilija Tovilo <tovilo.ilija@gmail.com> wrote:

> Hi everyone
>
> I'd like to propose a simple RFC to introduce looking up class
> constants by name. We have dedicated syntax for basically all other
> language constructs. This RFC aims to get rid of this seemingly
> arbitrary limitation.
>
> https://wiki.php.net/rfc/dynamic_class_constant_fetch
>
> Please let me know if you have any thoughts.
>

The proposal looks reasonable to me. While I wouldn't expect this syntax to
see much use, it does remove a syntactical inconsistency in the language.

> Order of execution

See
https://www.npopov.com/2017/04/14/PHP-7-Virtual-machine.html#writes-and-memory-safety
for why the order of execution is the way it is. As class constants do not
support writes, these concerns do not apply, and the "normal" order can be
used (as you propose).

Regards,
Nikita

--000000000000c3a8cd05ecd2d9de--