Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124750
Message-ID: <9c795377ff0983cc10bf108c68b12c0a1a693cc1.camel@ageofdream.com>
Subject: Re: [PHP-DEV] [RFC] Add Directive to Make All Namespaced Function
 Calls Global
To: internals@lists.php.net
Date: Sun, 04 Aug 2024 14:37:35 -0400
In-Reply-To: <53d4d4235e45fbe471179f4b95207a73890e9384.camel@ageofdream.com>
References: <d9c62789e46d1f3bbb67b9c966bb613661f7889b.camel@ageofdream.com>
	 <803741ef-7b51-4a92-8368-41e47f7783ab@gmail.com>
	 <53d4d4235e45fbe471179f4b95207a73890e9384.camel@ageofdream.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
Precedence: bulk
MIME-Version: 1.0
From: lists@ageofdream.com (Nick Lockheart)

> My thought was that it would have some clean and simple syntax, like:
>=20
> namespace foo using global functions;
> class MyClass{
>=20
> }
>=20
> When the parser hits that token, it just sets a flag and acts like
> every unqualified classname has a backslash in front of it.
>=20
> For everyone else:
>=20
> namespace foo;
> class MyClass{
>=20
> }
>=20
> ...would still work exactly the same as it does now. And would keep
> BC.

Edit: Meant to say "function name" not "class name", sorry.