Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125109
Message-ID: <a0db04a7fa1d9c77b9d2b0110b50a47ef959e98f.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 04:08:25 -0400
In-Reply-To: <790534cd-e158-4712-878c-642dfd0e2bad@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>
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
> If we were to go with any major change in the current lookup where it
> is perf or nothing, this is what I would propose for php 9.0
> (starting with an immediate deprecation):
> =C2=A0=C2=A0=C2=A01. any unqualified call simply calls the current namesp=
ace
> =C2=A0=C2=A0=C2=A02. >=3D php 9.0: no fallback to global
> =C2=A0=C2=A0=C2=A03. < php 9.0: emit deprecation notice if falls back to =
global
> This is how classes work (pretty sure), so it would be consistent.
>=20
> Going the other way (global first) doesn't really make sense because
> it is inconsistent, IMHO. Will it suck? Probably. Will it be easy to
> fix? Probably via Rector.
>=20
> =E2=80=94 Rob


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.

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.

Functions that are *not* on the built-in function list could default to
the local namespace.