Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126795
Message-ID: <1E14CA0A-0612-4D6B-8D50-5DEA0C546F3D@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_92496AE3-1E72-42E6-8CB1-A6AE830EB5AC"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Subject: Re: [PHP-DEV] RFC: short and inner classes
Date: Sun, 16 Mar 2025 22:04:53 +0100
In-Reply-To: <0F1E4400-5E26-4E39-88B9-ABD7ABBAEBC4@rwec.co.uk>
Cc: internals@lists.php.net
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
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>
From: claude.pache@gmail.com (Claude Pache)


--Apple-Mail=_92496AE3-1E72-42E6-8CB1-A6AE830EB5AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 15 mars 2025 =C3=A0 12:53, Rowan Tommins [IMSoP] =
<imsop.php@rwec.co.uk> a =C3=A9crit :
>=20
>=20
>=20
> 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 have to hope the programmers are using a style that makes it =
obvious what are inner classes and what are constants/methods.
>=20
> 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 "::"
>=20
> 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.)
>=20

According to my archeological research, it was originally designed to =
reuse `::` as namespace separator, but it was finally changed to =
something 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=

--Apple-Mail=_92496AE3-1E72-42E6-8CB1-A6AE830EB5AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>Le 15 mars 2025 =C3=A0 12:53, Rowan Tommins [IMSoP] =
&lt;imsop.php@rwec.co.uk&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div><div><br><br>On 14 March 2025 =
23:37:08 GMT, Rob Landers &lt;rob@bottled.codes&gt; =
wrote:<br><blockquote type=3D"cite">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 have to hope the programmers 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 =
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 "::"<br><br>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.)<br><br></div></div></blockquote><div><br></div><div>According to my =
archeological research, it was originally designed to reuse `::` as =
namespace separator, but it was finally changed to something else due to =
ambiguity between static class elements and namespaced =
functions/constants. See&nbsp;<a =
href=3D"https://wiki.php.net/rfc/namespaceissues">https://wiki.php.net/rfc=
/namespaceissues</a>&nbsp;and&nbsp;<a =
href=3D"https://wiki.php.net/rfc/backslashnamespaces">https://wiki.php.net=
/rfc/backslashnamespaces</a>&nbsp;(where `::` is assumed to be the =
namespace =
separator).</div><div><br></div><div>=E2=80=94Claude</div></div></body></h=
tml>=

--Apple-Mail=_92496AE3-1E72-42E6-8CB1-A6AE830EB5AC--