Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125127
Content-Type: text/plain;
	charset=us-ascii
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order (global,
 then local)
In-Reply-To: <838adce3-12da-49f3-88f2-883d63e93e89@app.fastmail.com>
Date: Fri, 23 Aug 2024 08:04:22 -0400
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <86C995C8-AFF0-4E4B-8385-69BC701B887E@newclarity.net>
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>
 <DACF099F-3CC9-4B92-9C4C-736B92E8D69C@newclarity.net>
 <838adce3-12da-49f3-88f2-883d63e93e89@app.fastmail.com>
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
From: mike@newclarity.net (Mike Schinkel)



> On Aug 23, 2024, at 7:50 AM, Rowan Tommins [IMSoP] =
<imsop.php@rwec.co.uk> wrote:
>=20
> On Fri, 23 Aug 2024, at 12:29, Mike Schinkel wrote:
>> namespace \AcmeComponents\SplineReticulator\Utilities\Text
>>=20
>> function Foo():int {
>> 	return Text\strlen("Hello World");
>> }
>>=20
>> The above of course could result in BC breaks IF there happened to be=20=

>> existing code that referenced Text\strlen() where Text was a =
top-level=20
>> namespace
>=20
> It wouldn't be a top-level namespace that would cause a conflict, but =
a nested one: currently the above code resolves the function name as =
"AcmeComponents\SplineReticulator\Utilities\Text\Text\strlen" (note the =
"...\Text\Text\...").

How often does that really occur in the wild? =20

And how can it occur without an explicit `use =
AcmeComponents\SplineReticulator\Utilities\Text\Text` statement, which I =
proposed would override the automatic `use`, anyway?

> It's an interesting suggestion, but I'm not totally sold on "use the =
end of the current namespace" being easier to remember than "use this =
symbol or keyword".
>=20
> return namespace\strlen("Hello World"); # current syntax, rather long =
and unclear
> return _\strlen("Hello World"); # short, but maybe a bit cryptic
> return Text\strlen("Hello World"); # variable length, relies on =
current context
> return NS\strlen("Hello World"); # shortening of current keyword
> return self\strlen("Hello World"); # maybe confusing to reuse a =
keyword?
> return current\strlen("Hello World"); # clear, but a bit long

The only one of those that has a strong analog to existing PHP code is =
to "use the end of the current namespace" as people frequently do with =
explicit `use` statements.

Yes, `self` has a weak analog to `self::`, but none of the others even =
come close, IMO. And adding `self\` may have unintended to the language, =
some slight BC concerns, and/or downstream consequences for other =
projects  vs. a simple automatic `use`.

Lastly, no comment on `\\`?

-Mike=