Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126777
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 15 Mar 2025 11:35:46 +0100
To: internals@lists.php.net
Message-ID: <9a6ebdaf-596b-45e1-8214-ca39276890bf@app.fastmail.com>
In-Reply-To: <d57e7a02-8678-415d-9f9c-b61bf8524b7a@app.fastmail.com>
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <70f34dcf-e4b6-4d92-8417-83ebeb03153c@rwec.co.uk>
 <d57e7a02-8678-415d-9f9c-b61bf8524b7a@app.fastmail.com>
Subject: Re: [PHP-DEV] RFC: short and inner classes
Content-Type: multipart/alternative;
 boundary=4a642c9c8e7b42acb6f563b01e895a73
From: rob@bottled.codes ("Rob Landers")

--4a642c9c8e7b42acb6f563b01e895a73
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 15, 2025, at 01:01, Rob Landers wrote:
>=20
>=20
> On Sat, Mar 15, 2025, at 00:21, Rowan Tommins [IMSoP] wrote:
>> On 05/03/2025 23:11, Rob Landers wrote:
>> >
>> > I'd like to introduce my RFC for discussion:=20
>> > https://wiki.php.net/rfc/short-and-inner-classes
>>=20
>>=20
>> As a user, I find the concept of inner classes quite confusing.
>>=20
>> However, I was looking at some code earlier and thought an "inner enu=
m"=20
>> would be useful, to replace various "MODE_FOO" type class constants -=20
>> but I see those are left to future scope. :(
>=20
> Actually, it appears I did not limit it in the implementation... So, m=
aybe we could play with it and see what breaks. I simply left traits, en=
ums, and interfaces to future scope because 1) I didn't have a working i=
mplementation yet, 2) had no idea what would break and 3) every time som=
eone suggests a change to enums, the discussion explodes.
>=20
> Having inner enums, traits, and interfaces is actually quite simple. M=
ight as well see how simple. :) But fwiw, I do plan on a near immediate =
RFC(s) for these if this thing passes, as well as short classes -- I als=
o have a semi-finished draft with short enums as well, but that one is a=
ctually physically impossible without making 'enum' a true reserved word=
. The "hack" (if you will) to bypass that requirement is still in place =
and makes the grammar (likely) impossible.
>=20
> I will have to fix this tomorrow, because I am not a fan of having inn=
er classes on interfaces, at least. I will play with it on enums and tra=
its and see what breaks. I suspect inner classes on traits will cause ut=
ter chaos.
>=20
>> I'm aware they exist in a lot of other languages, though, so I though=
t=20
>> I'd look around at how the proposed version compares. It seems there'=
s=20
>> quite a zoo out there...
>>=20
>> One common theme I do note is that all four of the pages I found are=20
>> titled "nested classes" or "nested types"; in some cases, "inner=20
>> class"/"inner type" has a specific meaning, which I don't think match=
es=20
>> the RFC's proposal.
>=20
> I actually borrowed heavily from C#. I'm familiar with its usage and r=
ules, and it fits nicely with PHP paradigms.
>=20
> =E2=80=94 Rob

After playing around with it in enums, traits, and even interfaces, I've=
 decided to allow it in them all. I've updated the RFC, fixed an issue i=
n the implementation, and clarified some poorly worded sections. I've al=
so added more realistic examples.

=E2=80=94 Rob
--4a642c9c8e7b42acb6f563b01e895a73
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">=0Ap.=
MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sat, Mar =
15, 2025, at 01:01, Rob Landers wrote:<br></div><blockquote type=3D"cite=
" id=3D"qt" style=3D""><div><br></div><div><br></div><div>On Sat, Mar 15=
, 2025, at 00:21, Rowan Tommins [IMSoP] wrote:<br></div><blockquote type=
=3D"cite" id=3D"qt-qt" style=3D""><div>On 05/03/2025 23:11, Rob Landers =
wrote:<br></div><div>&gt;<br></div><div>&gt; I'd like to introduce my RF=
C for discussion:&nbsp;<br></div><div>&gt;&nbsp;<a href=3D"https://wiki.=
php.net/rfc/short-and-inner-classes">https://wiki.php.net/rfc/short-and-=
inner-classes</a><br></div><div><br></div><div><br></div><div>As a user,=
 I find the concept of inner classes quite confusing.<br></div><div><br>=
</div><div>However, I was looking at some code earlier and thought an "i=
nner enum"&nbsp;<br></div><div>would be useful, to replace various "MODE=
_FOO" type class constants -&nbsp;<br></div><div>but I see those are lef=
t to future scope. :(<br></div></blockquote><div><br></div><div>Actually=
, it appears I did not limit it in the implementation... So, maybe we co=
uld play with it and see what breaks. I simply left traits, enums, and i=
nterfaces to future scope because 1) I didn't have a working implementat=
ion yet, 2) had no idea what would break and 3) every time someone sugge=
sts a change to enums, the discussion explodes.<br></div><div><br></div>=
<div>Having inner enums, traits, and interfaces is actually quite simple=
. Might as well see how simple. :) But fwiw, I do plan on a near immedia=
te RFC(s) for these if this thing passes, as well as short classes -- I =
also have a semi-finished draft with short enums as well, but that one i=
s actually physically impossible without making 'enum' a true reserved w=
ord. The "hack" (if you will) to bypass that requirement is still in pla=
ce and makes the grammar (likely) impossible.<br></div><div><br></div><d=
iv>I will have to fix this tomorrow, because I am not a fan of having in=
ner classes on interfaces, at least. I will play with it on enums and tr=
aits and see what breaks. I suspect inner classes on traits will cause u=
tter chaos.<br></div><div><br></div><blockquote type=3D"cite" id=3D"qt-q=
t" style=3D""><div>I'm aware they exist in a lot of other languages, tho=
ugh, so I thought&nbsp;<br></div><div>I'd look around at how the propose=
d version compares. It seems there's&nbsp;<br></div><div>quite a zoo out=
 there...<br></div><div><br></div><div>One common theme I do note is tha=
t all four of the pages I found are&nbsp;<br></div><div>titled "nested c=
lasses" or "nested types"; in some cases, "inner&nbsp;<br></div><div>cla=
ss"/"inner type" has a specific meaning, which I don't think matches&nbs=
p;<br></div><div>the RFC's proposal.<br></div></blockquote><div><br></di=
v><div>I actually borrowed heavily from C#. I'm familiar with its usage =
and rules, and it fits nicely with PHP paradigms.<br></div><div><br></di=
v><div id=3D"qt-sig121229152">=E2=80=94 Rob<br></div></blockquote><div><=
br></div><div>After playing around with it in enums, traits, and even in=
terfaces, I've decided to allow it in them all. I've updated the RFC, fi=
xed an issue in the implementation, and clarified some poorly worded sec=
tions. I've also added more realistic examples.<br></div><div><br></div>=
<div id=3D"sig121229152">=E2=80=94 Rob<br></div></body></html>
--4a642c9c8e7b42acb6f563b01e895a73--