Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125114
Message-ID: <d8bf24792d307d07863176772fbf35ec701b6b4b.camel@ageofdream.com>
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order
 (global, then local)
To: internals@lists.php.net
Date: Fri, 23 Aug 2024 05:34:06 -0400
In-Reply-To: <d26516d7-afaa-4174-81f0-361785908967@app.fastmail.com>
References: 
	<CAPyj-LCoBY2bPHLmsyONYDbY9aRSraLz5QNskeTiWfpMD0pTSg@mail.gmail.com>
	 <c385b525-37f7-446b-aa96-72272ef9e407@app.fastmail.com>
	 <CAPyj-LA4kTJTrQZUkn9kNMvWdH6SsFGU5mBO6EcpuUcRpXesgw@mail.gmail.com>
	 <d4b18a48-93b0-49c8-821d-f9298e831188@rwec.co.uk>
	 <BD6D644E-A90C-49B8-B51A-C9D4C943FDF6@newclarity.net>
	 <846D7756-712B-4A7C-9FC6-DB9F858836B8@rwec.co.uk>
	 <880ffc27dc9b421407a670c75d5f5ba756870396.camel@ageofdream.com>
	 <790534cd-e158-4712-878c-642dfd0e2bad@app.fastmail.com>
	 <a0db04a7fa1d9c77b9d2b0110b50a47ef959e98f.camel@ageofdream.com>
	 <d26516d7-afaa-4174-81f0-361785908967@app.fastmail.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)

> >=20
> >=20
> > A third option, which I haven't seen come up on the list yet, is
> > that
> > unqualified functions that are PHP built-ins are treated as global,
> > and
> > using a function having the same name as a built-in, in a namespace
> > scope, requires a fully qualified name to override the built-in.
> >=20
> > It seems that if someone is writing `array_key_exists()` or similar
> > they probably mean the built-in function, and in the rare cases
> > where
> > they do mean `\foo\array_key_exists()`, they can write it
> > explicitly.
> >=20
> > Functions that are *not* on the built-in function list could
> > default to
> > the local namespace.
>=20
> I was actually thinking of doing something like this for function
> autoloading, where extensions could register global functions that
> bypass the autoloader and go straight to global if it isn't defined
> in the local namespace already. I decided not to even bring it up
> because it felt controversial (it would effectively be global first,
> except for user functions). Though, it might be a nice compromise?
>=20
> =E2=80=94 Rob


I think we are all trying to achieve the same thing here.

There's different ways to go about it, each with pros and cons, but I
think we need to think through how all the parts fit together, because
I think if we can reach consensus, then several RFCs become compatible
with each other.

A change to how function namespace lookup works would affect function
auto-loading, and it may even make it simpler, depending on the other
options that we end up going with.