Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125199
Date: Sat, 24 Aug 2024 22:23:20 -0400
To: Ilija Tovilo <tovilo.ilija@gmail.com>, PHP internals
 <internals@lists.php.net>
Message-ID: <11D68C16-751E-4FBE-ACB8-F95ABC5190F2@edison.tech>
In-Reply-To: <CAPyj-LAW3F7yVD=Yrd2q2pq-F7VKwNfba40kF-SjS=71MaJ_Fw@mail.gmail.com>
References: <CAPyj-LDCdo+UE0W1q6LOAVHrt6mVmGft9K4mBDvjkBWR3TT4kA@mail.gmail.com>
 <E44D36DF-CE24-46CC-8705-47C3F7EFC123@getmailspring.com>
 <CAPyj-LAW3F7yVD=Yrd2q2pq-F7VKwNfba40kF-SjS=71MaJ_Fw@mail.gmail.com>
Subject: Re: [PHP-DEV] [Concept] Flip relative function lookup order
 (global, then local)
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="66ca9598_327b23c6_90b0"
From: mike@newclarity.net (Mike Schinkel)

--66ca9598_327b23c6_90b0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

     =20
 =20

 =20
 =20
 =20
 =20
>  =20
> On Aug 23, 2024 at 2:30 PM,  <Ilija Tovilo (mailto:tovilo.ilija=40gmail=
.com)>  wrote:
>  =20
>  =20
>  =20
>  On =46ri, Aug 23, 2024 at 8:19=E2=80=AFPM John Coggeshall  <john=40cog=
geshall.org>  wrote:  >   >  1. People who don't think BC is a problem, a=
nd would like to drop  >  either the global or local lookup entirely, req=
uiring disambiguation.  >   >  There is also an option of swapping the pr=
iority, making local lookups secondary to global lookups -- and to overri=
de that behavior you would require disambiguation. It doesn't have to mea=
n drop the lookup entirely. Right, that's my proposal. My point was that =
few (nobody except you and me, I believe) showed particular excitement fo=
r this approach. =20
>  =20
>  =20
>    =20
>  =20
>    =20
>  =20
>      =20

 There is also the 5th (or 4th=3F) option of making built-ins special and=
 not require them nor locals be prefixed, and instead require global user=
land functions to be prefixed. =20
>  =20
 =20
 =20
 =20

 =20
-Mike
 =20
     
--66ca9598_327b23c6_90b0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html><body><div id=3D=22edo-message=22><div></div></div><div id=3D=22edo=
-original=22><div><blockquote type=3D=22cite=22 style=3D=22margin:1ex 0 0=
 0; height: min-content; border-left:1px =23ccc solid;padding-left:0.5ex;=
=22><div>On Aug 23, 2024 at 2:30 PM, &lt;<a href=3D=22mailto:tovilo.ilija=
=40gmail.com=22>Ilija Tovilo</a>&gt; wrote:<br><br></div><div><pre class=3D=
=22edo-pre=22>On =46ri, Aug 23, 2024 at 8:19=E2=80=AFPM John Coggeshall &=
lt;john=40coggeshall.org&gt; wrote:
&gt;
&gt; 1. People who don't think BC is a problem, and would like to drop
&gt; either the global or local lookup entirely, requiring disambiguation=
.
&gt;
&gt; There is also an option of swapping the priority, making local looku=
ps secondary to global lookups -- and to override that behavior you would=
 require disambiguation. It doesn't have to mean drop the lookup entirely=
.

Right, that's my proposal. My point was that few (nobody except you
and me, I believe) showed particular excitement for this approach.
</pre><pre class=3D=22edo-pre=22><br></pre><pre class=3D=22edo-pre=22><br=
></pre><pre class=3D=22edo-pre=22><br></pre></div></blockquote><div id=3D=
=22edo-original=22><br>There is also the 5th (or 4th=3F) option of making=
 built-ins special and not require them nor locals be prefixed, and inste=
ad require global userland functions to be prefixed.<blockquote type=3D=22=
cite=22 style=3D=22margin: 1ex 0px 0px; height: min-content; border-left-=
width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 20=
4); padding-left: 0.5ex;=22></blockquote></div></div><div id=3D=22edo-ori=
ginal=22><br></div><div id=3D=22edo-original=22>-Mike</div></div></body><=
/html>
--66ca9598_327b23c6_90b0--