Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124724
Message-ID: <a84bfb9a67145e7e8164c8dc2b7a4ec4fe6fe53f.camel@ageofdream.com>
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order
 (global, then local)
To: internals@lists.php.net
Date: Fri, 02 Aug 2024 14:46:03 -0400
In-Reply-To: <6F2E44FA-4E00-47F9-BD56-5051385E3673@rwec.co.uk>
References: 
	<CAPyj-LCoBY2bPHLmsyONYDbY9aRSraLz5QNskeTiWfpMD0pTSg@mail.gmail.com>
	 <b853e1a8b0e46f3b0115ca3790551575b5119af4.camel@ageofdream.com>
	 <6F2E44FA-4E00-47F9-BD56-5051385E3673@rwec.co.uk>
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 Fri, 2024-08-02 at 18:53 +0100, Rowan Tommins [IMSoP] wrote:
>=20
>=20
> On 2 August 2024 18:19:41 BST, Nick Lockheart <lists@ageofdream.com>
> wrote:
> > I had suggested a per-file directive in a post to this list a while
> > back. Something like:
> >=20
> > namespace foo;
> > use global functions;
>=20
> There was a proposal for exactly this a few years ago, which ended up
> in an RFC with a slightly different syntax (using a declare()
> statement), but was declined in voting by 35 votes to 2.
>=20
> I can't remember much about the discussion, so am not sure what
> changes would make a new attempt more likely to pass.
>=20
> Regards,
> Rowan Tommins
> [IMSoP]

In all likelihood, it was the syntax that was disfavored.

What about an RFC where we vote on if the feature should exist, without
any syntax?

ie. "Should there be a way for developers to signal to the parser that
all functions should be treated as global and skip NS lookup, and use
dedicated opcodes? The specific syntax would be decided in a different
RFC/vote if this one passes."

Yes: We should do this, let's discuss syntax possibilities.
No: This should not be a feature at all.