Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110643
MIME-Version: 1.0
References: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@mail.gmail.com>
In-Reply-To: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@mail.gmail.com>
Date: Wed, 17 Jun 2020 23:18:23 -0500
Message-ID: <CAEUnE0eF7mb-B+eTw40+TJyk_bq8vR5gBy+enHVWdq74PWX=CA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e099e405a8541110"
Subject: Re: [PHP-DEV] [RFC] Treat namespaced names as single token, relax
 reserved keyword restrictions
From: tendoaki@gmail.com (Michael Morris)

--000000000000e099e405a8541110
Content-Type: text/plain; charset="UTF-8"

What other language allows this? None that I can think of. Do we want PHP
doing something it's most closely related languages do not allow?  Why
don't they allow this? What problems are we creating by allowing this? I
can imagine this would make autoloading functions and constants by
namespace more complicated, but I'm not sure.

On Tue, Jun 16, 2020 at 3:52 AM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> Inspired by the recent discussion on reserved keyword reservation, I'd like
> to propose the following RFC:
>
> https://wiki.php.net/rfc/namespaced_names_as_token
>
> 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.
>
> 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.
>
> Regards,
> Nikita
>

--000000000000e099e405a8541110--