Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110505
MIME-Version: 1.0
References: <CAPyj-LCW_XhUHwp+5O0JUxcnC4ABtZYccbvi8a5uPL9Bb5PScQ@mail.gmail.com>
In-Reply-To: <CAPyj-LCW_XhUHwp+5O0JUxcnC4ABtZYccbvi8a5uPL9Bb5PScQ@mail.gmail.com>
Date: Sat, 13 Jun 2020 22:32:51 +0300
Message-ID: <CAJW__o3XjBCsvPgnb8wQZDvSzG9=Empm8ouz4pmev8Qzc2VPMg@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Reserve keywords in PHP 8
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

Den l=C3=B8r. 13. jun. 2020 kl. 22.10 skrev Ilija Tovilo <tovilo.ilija@gmai=
l.com>:
>
> Hi internals
>
> I created a new RFC for reserving keywords we might need in PHP 8.x versi=
ons.
> https://wiki.php.net/rfc/reserve_keywords_in_php_8
>
> Let me know if there's something you'd like to work on that will
> require a keyword and I will add it to the list. The keywords will
> most likely be voted on separately.

I do not see a point in soft reserving something we don't even know if
it will make it into 8.x. I mean sure you might work on some of them,
but they should be voted on a case by case basis. We did future
reserve somethings in the past for PHP6, e.g. the "b" string prefix
and the "(binary)" cast (for the then non unicode strings). See:
https://3v4l.org/nFJHb We stopped trying to future proof code by soft
reserving after PHP6 turned out to be nothing and most of the features
were ported to PHP5.3. I don't think we should go down that path again
of soft reserving something before we can guarantee it will be
implemented, something we cannot currently until it is voted in.

--=20
regards,

Kalle Sommer Nielsen
kalle@php.net