Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110645
Message-ID: <870E22A7-879D-415C-B7D0-71560B9CE156@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_5CC91CDD-EC1C-43E5-9BE0-177169D4CF7A"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 18 Jun 2020 08:44:32 +0200
In-Reply-To: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@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>
Subject: Re: [PHP-DEV] [RFC] Treat namespaced names as single token, relax
 reserved keyword restrictions
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_5CC91CDD-EC1C-43E5-9BE0-177169D4CF7A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

The following part of the proposal is problematic: Allow keywords in =
definition of classes, functions, const, etc.

class KEYWORD {}
interface KEYWORD {}
trait KEYWORD {}
function KEYWORD() {}
const KEYWORD =3D 0;
use Foo as KEYWORD;
Under your proposal, the following code will compile without notice, but =
will have a different behaviour from what the programmer intended:

```php
class Int { }

const PRINT =3D 2;
const YIELD =3D 3;

function foo(Int $b) {
    return PRINT + YIELD;
}
```

If it is important to allow to define classes, etc. with a keyword as =
name, I suggest to force the programmer to say explicitly =E2=80=9CYes, =
it is really what I want=E2=80=9D. For example, something like the =
following:

```php
class namespace\Int { }

const namespace\PRINT =3D 2;
```

Another point which is problematic, is to allow `namespace` as a =
namespace parts, since `namespace\foo`, although interpreted as a =
namespace-relative name, could be intended to be a qualified name by the =
programmer.

=E2=80=94Claude




> Le 16 juin 2020 =C3=A0 10:52, Nikita Popov <nikita.ppv@gmail.com> a =
=C3=A9crit :
>=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
> Regards,
> Nikita


--Apple-Mail=_5CC91CDD-EC1C-43E5-9BE0-177169D4CF7A--