Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126593
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 06 Mar 2025 07:23:21 +0100
To: "Juris Evertovskis" <juris@glaive.pro>, internals@lists.php.net
Message-ID: <ac0f8436-a960-4866-a5f6-f4c9a0e81589@app.fastmail.com>
In-Reply-To: <076001db8e34$41cab990$c5602cb0$@glaive.pro>
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <076001db8e34$41cab990$c5602cb0$@glaive.pro>
Subject: Re: [PHP-DEV] RFC: short and inner classes
Content-Type: multipart/alternative;
 boundary=8e38d8e6c15041189e2d0aea3d161f68
From: rob@bottled.codes ("Rob Landers")

--8e38d8e6c15041189e2d0aea3d161f68
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Thu, Mar 6, 2025, at 02:08, Juris Evertovskis wrote:
> Hi,
> =20
> Maybe I didn=E2=80=99t read the RFC carefully enough, but=E2=80=A6 Do =
any of these features require the other one?
> =20
> I=E2=80=99m asking because I wouldn=E2=80=99t want to see them both de=
nied just because the voters disagree with one of them.
> =20
> Good luck with this proposal!
> =20
> Juris

Hi Juris,

Yes and no. Without the short syntax, classes explode in size if you jus=
t want to have simple inner classes for DTO/organization. For example, I=
 used this for quite a bit over the last couple of weeks. One big usage,=
 from my experiments, was to replace array returns:

class StringList(public array $strings);

And it makes it =E2=80=9Ceasy on the eyes=E2=80=9D to just have a list o=
f classes at the top of the class. By itself, a short syntax makes some =
sense, but isn=E2=80=99t compelling (IMHO), and inner classes cause an e=
xplosion in LoC without it.

So, technically, they aren=E2=80=99t required to be in the same RFC; but=
 also, they complement each other very well.

If the RFC fails due to them being together, I=E2=80=99ll take the feedb=
ack and go back to the drawing board.

=E2=80=94 Rob
--8e38d8e6c15041189e2d0aea3d161f68
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">#qt p=
.qt-MsoNormal{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-l=
eft:0cm;font-size:12pt;font-family:Aptos, sans-serif;}=0A=0Ap.MsoNormal,=
p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div><br></d=
iv><div>On Thu, Mar 6, 2025, at 02:08, Juris Evertovskis wrote:<br></div=
><blockquote type=3D"cite" id=3D"qt" style=3D"overflow-wrap:break-word;"=
><div class=3D"qt-WordSection1"><div><p class=3D"qt-MsoNormal"><span cla=
ss=3D"size" style=3D"font-size:11pt;">Hi,</span><br></p><p class=3D"qt-M=
soNormal"><span class=3D"size" style=3D"font-size:11pt;">&nbsp;</span><b=
r></p><p class=3D"qt-MsoNormal"><span class=3D"size" style=3D"font-size:=
11pt;">Maybe I didn=E2=80=99t read the RFC carefully enough, but=E2=80=A6=
 Do any of these features require the other one?</span><br></p><p class=3D=
"qt-MsoNormal"><span class=3D"size" style=3D"font-size:11pt;">&nbsp;</sp=
an><br></p><p class=3D"qt-MsoNormal"><span class=3D"size" style=3D"font-=
size:11pt;">I=E2=80=99m asking because I wouldn=E2=80=99t want to see th=
em both denied just because the voters disagree with one of them.</span>=
<br></p><p class=3D"qt-MsoNormal"><span class=3D"size" style=3D"font-siz=
e:11pt;">&nbsp;</span><br></p><p class=3D"qt-MsoNormal"><span class=3D"s=
ize" style=3D"font-size:11pt;">Good luck with this proposal!</span><br><=
/p><p class=3D"qt-MsoNormal"><span class=3D"size" style=3D"font-size:11p=
t;">&nbsp;</span><br></p><p class=3D"qt-MsoNormal"><span class=3D"size" =
style=3D"font-size:11pt;">Juris</span><br></p></div></div></blockquote><=
div><br></div><div>Hi Juris,<br></div><div><br></div><div>Yes and no. Wi=
thout the short syntax, classes explode in size if you just want to have=
 simple inner classes for DTO/organization. For example, I used this for=
 quite a bit over the last couple of weeks. One big usage, from my exper=
iments, was to replace array returns:<br></div><div><br></div><div>class=
 StringList(public array $strings);<br></div><div><br></div><div>And it =
makes it =E2=80=9Ceasy on the eyes=E2=80=9D to just have a list of class=
es at the top of the class. By itself, a short syntax makes some sense, =
but isn=E2=80=99t compelling (IMHO), and inner classes cause an explosio=
n in LoC without it.<br></div><div><br></div><div>So, technically, they =
aren=E2=80=99t required to be in the same RFC; but also, they complement=
 each other very well.<br></div><div><br></div><div>If the RFC fails due=
 to them being together, I=E2=80=99ll take the feedback and go back to t=
he drawing board.</div><div><br></div><div id=3D"sig121229152">=E2=80=94=
 Rob<br></div></body></html>
--8e38d8e6c15041189e2d0aea3d161f68--