Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123540
Content-Type: text/plain;
	charset=utf-8
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: [PHP-DEV] RFC proposal : "new" keyword shorthand
In-Reply-To: <CAMuyDGP58tTGWiTN=e22x7A5DXxE7UTZ1X2No+zcf6sYUc4wmg@mail.gmail.com>
Date: Fri, 7 Jun 2024 12:30:39 -0400
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <3B435D7E-774A-451E-AE52-768A1DB273D8@zort.net>
References: <CAMuyDGP58tTGWiTN=e22x7A5DXxE7UTZ1X2No+zcf6sYUc4wmg@mail.gmail.com>
To: =?utf-8?Q?Beno=C3=AEt_Condaminet?= <condaminet.benoit@gmail.com>
From: jbafford@zort.net (John Bafford)

Hi Beno=C3=AEt,

> On Jun 7, 2024, at 12:03, Beno=C3=AEt Condaminet =
<condaminet.benoit@gmail.com> wrote:
>=20
> As a first try, I start updated code to completely make the new =
keyword optional, like in Dart language for example, but it require very =
big change, with lot of impact (collision with function).=20
>=20
> So here is my proposal :=20
>=20
> Add a "new" shorthand, using the tilde character : "~"
> I made a POC, and it works well, declaring a new language token =
T_SHORT_NEW that simply reuse ZEND_AST_NEW under the hood.

I would point out that ~ is an existing operator, bitwise not. Is there =
not the same ambiguity with that as with not having the new keyword at =
all? Because PHP has classes and functions in different namespaces =
~SomeClass() looks exactly the same as ~SomeFunction(), and ~$someVar() =
would be just as ambiguous.

I would prefer to see the new keyword go away as well, but as long as =
functions and classes are in separate namespaces, that might be =
difficult.

-John=