Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125144
Content-Type: text/plain;
	charset=us-ascii
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order (global,
 then local)
In-Reply-To: <0d269a38-28fe-494c-a903-50022e09f27b@app.fastmail.com>
Date: Fri, 23 Aug 2024 21:04:32 +0700
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E848530A-038F-40E0-A87D-D0C823C5E967@koalephant.com>
References: <21D6F160-5EAE-44FA-907B-E1DAAC1B8D75@rwec.co.uk>
 <53BD062A-4D7F-4E5D-852E-6D27641213A8@koalephant.com>
 <f32382b4-3bee-47ab-88ed-ad2ab154c319@app.fastmail.com>
 <7607FD64-5572-466E-9866-63C2536B2A09@koalephant.com>
 <0d269a38-28fe-494c-a903-50022e09f27b@app.fastmail.com>
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
From: php-lists@koalephant.com (Stephen Reay)



> On 23 Aug 2024, at 20:20, Rowan Tommins [IMSoP] <imsop.php@rwec.co.uk> =
wrote:
>=20
> On Fri, 23 Aug 2024, at 13:43, Stephen Reay wrote:
>> This change would also break existing code that does "the right =
thing",=20
>> and has the potential to arbitrarily break perfectly valid userland=20=

>> code *any time a new global function is added*, forever.
>=20
> You replied to me, but you seem to be commenting on one of the other =
proposals. My preference is for "unqualified =3D global", which is a =
one-off breaking change, which only affects user-defined functions, =
which are declared in a namespace, and used in that same namespace.
>=20
> You're right that it would mean classes and functions resolve =
differently, and that's why I said that if I had a time machine, I would =
support a different option. But, personally, I don't think the small =
long-term inconsistency outweighs the huge short-term disruption of =
defaulting to local.
>=20
> Regards,
> --=20
> Rowan Tommins
> [IMSoP]
>=20

Ok well I apologise, I thought you were proposing whatever "current =
namespace" syntax solution as optional, rather required.


I stand by the rest of my argument though. This entire ridiculous =
discussion about a huge BC break that introduces bizarre =
inconsistencies, is 100% because a handful of people don't want to type =
`\`.

Are we going to go through this whole ridiculous dance for classes and =
interfaces and traits next too? They always need to be prepended with =
`\` (or imported), so I can't begin to imagine what horrors that must be =
presenting for those poor souls who are allergic to a leading backslash.


Perhaps next we can go back to having register_globals and forcing it to =
always on, because people don't want to type $_GET or $_POST. Perhaps =
after that we can bring back magic quotes because parameterised queries =
are too much to type?