Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124745
Message-ID: <36129ec6c439bdf3b1f882da89a2fd3a5249889a.camel@ageofdream.com>
Subject: Re: [PHP-DEV] [RFC] Add Directive to Make All Namespaced Function
 CallsGlobal
To: "Christoph M. Becker" <cmbecker69@gmx.de>, internals@lists.php.net
Date: Sun, 04 Aug 2024 14:04:22 -0400
In-Reply-To: <332927b9-8caf-4139-9e03-0ab267500745@gmx.de>
References: <d9c62789e46d1f3bbb67b9c966bb613661f7889b.camel@ageofdream.com>
	 <332927b9-8caf-4139-9e03-0ab267500745@gmx.de>
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)

On Sun, 2024-08-04 at 20:02 +0200, Christoph M. Becker wrote:
> On 04.08.2024 at 15:09, Nick Lockheart wrote:
>=20
> > To that end, I have created the following RFC:
> >=20
> > https://wiki.php.net/rfc/global_function_parser_directive
> > I am asking that we discuss and vote on the following question:
> >=20
> > =E2=80=9CShould there be some way for developers to signal to the parse=
r at
> > compile time that all unqualified function names found in a
> > namespace
> > context are global, without a namespace lookup?=E2=80=9D
> >=20
> > Yes: We should do this, let's discuss syntax possibilities.
> >=20
> > No: This should not be a feature at all.
>=20
> Thanks for the PR!
>=20
> However, it seems to me that the "syntax possibilites" are an
> important
> part of the vote.=C2=A0 Maybe all will agree that having that option is
> good,
> but there still might not even be consensus on the "syntax".
>=20
> Maybe just some straw poll to gauge interest in the general feature
> would be more appropriate?
>=20
> Christoph
>=20

That's exactly what this is: a straw poll on the feature itself.