Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125148
Date: Fri, 23 Aug 2024 12:13:52 -0400
To: =?utf-8?Q?Rowan_Tommins_=5BIMSoP=5D?= <imsop.php@rwec.co.uk>
Cc: "=?utf-8?Q?internals=40lists.php.net?=" <internals@lists.php.net>
Message-ID: <48F2A153-D33C-47CA-AB0A-67B85258D8E9@getmailspring.com>
In-Reply-To: <63DAE337-B117-4380-8735-186DC30FE0B7@rwec.co.uk>
References: <63DAE337-B117-4380-8735-186DC30FE0B7@rwec.co.uk>
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order
 (global, then local)
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="66c8b540_6b8b4567_15341"
From: john@coggeshall.org (John Coggeshall)

--66c8b540_6b8b4567_15341
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



On Aug 23 2024, at 11:49 am, Rowan Tommins [IMSoP] <imsop.php@rwec.co.uk> wrote:
>
> And most users don't object to using a leading backslash, they just (quite reasonably) have no idea what impact it has on the ability of the engine to optimise their code.

I think this is a misread, and I don't think you can argue that there is a clear understanding of "most users" here. While I admit I too don't have real data to back this up, I would be more likely to believe "most users" would absolutely object to being forced into using a leading backslash and would find it non-sensical that you must add a backslash for the engine to do the "right thing" (in this case, optimize their code with a security benefit), vs just doing the right thing by default.

--66c8b540_6b8b4567_15341
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div class=3D=22gmail=5Fquote=5Fattribution=22>On Aug 23 2024, at=
 11:49 am, Rowan Tommins =5BIMSoP=5D &lt;imsop.php=40rwec.co.uk&gt; wrote=
:</div><blockquote><div><br><div>And most users don't object to using a l=
eading backslash, they just (quite reasonably) have no idea what impact i=
t has on the ability of the engine to optimise their code.</div></div></b=
lockquote><div><br><div>I think this is a misread, and I don't think you =
can argue that there is a clear understanding of =22most users=22 here. W=
hile I admit I too don't have real data to back this up, I would be more =
likely to believe =22most users=22 would absolutely object to being force=
d into using a leading backslash and would find it non-sensical that you =
must add a backslash for the engine to do the =22right thing=22 (in this =
case, optimize their code with a security benefit), vs just doing the rig=
ht thing by default. </div><br></div>
--66c8b540_6b8b4567_15341--