Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126796
Precedence: bulk
MIME-Version: 1.0
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <AM8P250MB01709D7FC3E4FDF07E8995C2E2D22@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <4abd7008-ae33-46fe-8bbd-7c99f7c48158@app.fastmail.com> <0F1E4400-5E26-4E39-88B9-ABD7ABBAEBC4@rwec.co.uk>
 <1E14CA0A-0612-4D6B-8D50-5DEA0C546F3D@gmail.com>
In-Reply-To: <1E14CA0A-0612-4D6B-8D50-5DEA0C546F3D@gmail.com>
Date: Sun, 16 Mar 2025 23:21:35 +0200
Message-ID: <CAGwLL8VJKrLoom-GHMHq3CNfNJdWu0-qRZu6qH2S8PcTR51kAQ@mail.gmail.com>
Subject: Re: [PHP-DEV] RFC: short and inner classes
To: Claude Pache <claude.pache@gmail.com>
Cc: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000503ef906307c42af"
From: i.miroslavov@gmail.com (Iliya Miroslavov Iliev)

--000000000000503ef906307c42af
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Claude, exactly! By using '::' you cannot distinguish between a class and a
function. So this is not an option because it leads to a headache. Just my
2 cents

On Sun, Mar 16, 2025 at 11:08=E2=80=AFPM Claude Pache <claude.pache@gmail.c=
om>
wrote:

>
>
> Le 15 mars 2025 =C3=A0 12:53, Rowan Tommins [IMSoP] <imsop.php@rwec.co.uk=
> a
> =C3=A9crit :
>
>
>
> On 14 March 2025 23:37:08 GMT, Rob Landers <rob@bottled.codes> wrote:
>
> I could get behind `::`, but I feel that it introduces human ambiguity. I
> don't believe it would introduce compiler ambiguity, but as a human, I ha=
ve
> to hope the programmers are using a style that makes it obvious what are
> inner classes and what are constants/methods.
>
>
> As far as I can see, all four languages I looked up last night (Java, C#,
> Swift, Kotlin) use the same syntax for accessing a nested type as for
> accessing a property or method, so we'd be following the crowd to use "::=
"
>
> That said, I think they all also use that same syntax for namespace (or
> equivalent) lookups, so the same argument can be made for "\". (Why PHP
> separates those isn't entirely clear to me.)
>
>
> According to my archeological research, it was originally designed to
> reuse `::` as namespace separator, but it was finally changed to somethin=
g
> else due to ambiguity between static class elements and namespaced
> functions/constants. See https://wiki.php.net/rfc/namespaceissues and
> https://wiki.php.net/rfc/backslashnamespaces (where `::` is assumed to be
> the namespace separator).
>
> =E2=80=94Claude
>


--=20
Iliya Miroslavov Iliev
i.miroslavov@gmail.com

--000000000000503ef906307c42af
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Claude, exactly! By using &#39;::&#39; you cannot distingu=
ish between a class and a function. So this is not an option because it lea=
ds to a headache. Just my 2 cents</div><br><div class=3D"gmail_quote gmail_=
quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 16, 2025=
 at 11:08=E2=80=AFPM Claude Pache &lt;<a href=3D"mailto:claude.pache@gmail.=
com">claude.pache@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div><br id=3D"m_-1090547215002758986lineBreakAt=
BeginningOfMessage"><div><br><blockquote type=3D"cite"><div>Le 15 mars 2025=
 =C3=A0 12:53, Rowan Tommins [IMSoP] &lt;<a href=3D"mailto:imsop.php@rwec.c=
o.uk" target=3D"_blank">imsop.php@rwec.co.uk</a>&gt; a =C3=A9crit :</div><b=
r><div><div><br><br>On 14 March 2025 23:37:08 GMT, Rob Landers &lt;rob@bott=
led.codes&gt; wrote:<br><blockquote type=3D"cite">I could get behind `::`, =
but I feel that it introduces human ambiguity. I don&#39;t believe it would=
 introduce compiler ambiguity, but as a human, I have to hope the programme=
rs are using a style that makes it obvious what are inner classes and what =
are constants/methods.<br></blockquote><br>As far as I can see, all four la=
nguages I looked up last night (Java, C#, Swift, Kotlin) use the same synta=
x for accessing a nested type as for accessing a property or method, so we&=
#39;d be following the crowd to use &quot;::&quot;<br><br>That said, I thin=
k they all also use that same syntax for namespace (or equivalent) lookups,=
 so the same argument can be made for &quot;\&quot;. (Why PHP separates tho=
se isn&#39;t entirely clear to me.)<br><br></div></div></blockquote><div><b=
r></div><div>According to my archeological research, it was originally desi=
gned to reuse `::` as namespace separator, but it was finally changed to so=
mething else due to ambiguity between static class elements and namespaced =
functions/constants. See=C2=A0<a href=3D"https://wiki.php.net/rfc/namespace=
issues" target=3D"_blank">https://wiki.php.net/rfc/namespaceissues</a>=C2=
=A0and=C2=A0<a href=3D"https://wiki.php.net/rfc/backslashnamespaces" target=
=3D"_blank">https://wiki.php.net/rfc/backslashnamespaces</a>=C2=A0(where `:=
:` is assumed to be the namespace separator).</div><div><br></div><div>=E2=
=80=94Claude</div></div></div></blockquote></div><div><br clear=3D"all"></d=
iv><div><br></div><span class=3D"gmail_signature_prefix">-- </span><br><div=
 dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Iliya Miroslavov Il=
iev<div><a href=3D"mailto:i.miroslavov@gmail.com" target=3D"_blank"><font c=
olor=3D"#6aa84f">i.miroslavov@gmail.com</font></a><br></div></div></div>

--000000000000503ef906307c42af--