Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110998
Message-ID: <FA6992DC-91A6-4D62-A6CC-37BD4EBB12C4@stitcher.io>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_98A64921-C2A0-4401-9F2B-5318E83D3F65"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Tue, 14 Jul 2020 12:52:14 +0200
In-Reply-To: <CAF+90c_hjNrsOfesH=y4_cUPj5J2KsWH0e83xnrXsaV0eX_HLw@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@mail.gmail.com>
 <CAF+90c8m_4v_fdJfFMH+mHRf7qxps1zzrmCbVsAfQOjBmOhqFw@mail.gmail.com>
 <CAF+90c_hjNrsOfesH=y4_cUPj5J2KsWH0e83xnrXsaV0eX_HLw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Treat namespaced names as single token, relax
 reserved keyword restrictions
From: brendt@stitcher.io (Brent Roose)

--Apple-Mail=_98A64921-C2A0-4401-9F2B-5318E83D3F65
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Nikita

What happens to the attributes syntax if this RFC doesn't pass?

Furthermore, I think voting against this RFC to prevent the @@ syntax =
from happening is an abuse of the system. If there are problems with the =
attribute syntax, than the vote results on that one should be called =
void and a revote should happen, but it shouldn't affect the vote of =
this RFC, which has a larger impact than just the attributes syntax.

Kind regards
Brent



> On 14 Jul 2020, at 11:09, Nikita Popov <nikita.ppv@gmail.com> wrote:
>=20
> On Thu, Jul 9, 2020 at 4:33 PM Nikita Popov <nikita.ppv@gmail.com =
<mailto:nikita.ppv@gmail.com>> wrote:
>=20
>> On Tue, Jun 16, 2020 at 10:52 AM Nikita Popov <nikita.ppv@gmail.com>
>> wrote:
>>=20
>>> Hi internals,
>>>=20
>>> Inspired by the recent discussion on reserved keyword reservation, =
I'd
>>> like to propose the following RFC:
>>>=20
>>> https://wiki.php.net/rfc/namespaced_names_as_token
>>>=20
>>> This RFC makes two related changes: Treat namespaced names as a =
single
>>> token, which enables use of reserved keywords inside them. And =
remove
>>> reserved keyword restrictions from various declarations.
>>>=20
>>> The RFC comes with a small backwards compatibility break related to =
names
>>> that include whitespace, but will hopefully reduce the backwards
>>> compatibility impact of future reserved keyword additions.
>>>=20
>>=20
>> I have reduced the scope of this RFC to handle just the issue of
>> namespaced names, without touching any other reserved keyword =
restrictions.
>> As the discussion shows, those are trickier, with more cases of =
perceived
>> ambiguity that may need to be mitigated.
>>=20
>> As this proposal is now a prerequisite for
>> https://wiki.php.net/rfc/shorter_attribute_syntax, I have heard from =
a
>> disturbing number of people that they might vote against this =
proposal, not
>> because they disagree with it, but because that would prevent the =
adoption
>> of the @@ attribute syntax. I'm not sure what to do about that...
>>=20
>=20
> Heads up: I plan to open voting on this proposal tomorrow, unless =
there is
> further feedback.
>=20
> Nikita


--Apple-Mail=_98A64921-C2A0-4401-9F2B-5318E83D3F65--