Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124076
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-538-g1508afaa2-fm-20240616.001-g1508afaa
Precedence: bulk
MIME-Version: 1.0
Message-ID: <4e76abb0-72ed-4b1f-a5c8-163c76533bde@app.fastmail.com>
In-Reply-To: <2e7f87d2-a2a1-47f4-a1f0-31cf490a2edf@app.fastmail.com>
References: <256b79d4-713c-4547-953d-8bc8291da9f3@app.fastmail.com>
 <50B4D759-03D3-45CA-87C0-757AFC4B67D0@sakiot.com>
 <2e7f87d2-a2a1-47f4-a1f0-31cf490a2edf@app.fastmail.com>
Date: Sun, 30 Jun 2024 08:49:57 +0200
To: "Saki Takamachi" <saki@sakiot.com>
Cc: "Gina P. Banyard" <internals@gpb.moe>, internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Operator Overrides -- Lite Edition
Content-Type: multipart/alternative;
 boundary=72b2bf80d79049289577bf20c409068e
From: rob@bottled.codes ("Rob Landers")

--72b2bf80d79049289577bf20c409068e
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 30, 2024, at 06:59, Rob Landers wrote:
>=20
>=20
> On Sun, Jun 30, 2024, at 01:28, Saki Takamachi wrote:
>> Hi,
>>=20
>> > Hello internals,
>> >=20
>> > I've updated the RFC to include final-ish examples (barring any fur=
ther constructive feedback), a prototype implementation, and an objectio=
ns section.
>> >=20
>> > Cheers,
>> >=20
>> > Rob
>>=20
>> It seems like the "hack" I mentioned is still possible, am I misunder=
standing something?
>=20
> That=E2=80=99s always going to be a possibility, no matter what we do =
or how we do it. I think it would be a rather pointless hack now that I =
can run the code. For the most part, the engine treats these as numbers =
and trying to dodge that will land you in hot water eventually.=20

After playing with the code and seeing what I could get away with, makin=
g the GMP class `readonly` appears to prevent many abuses, so I have ame=
nded the RFC and prototype code.

>=20
>>=20
>> And I don't understand the purpose of polyfills at all. If you're not=
 using the GMP extensions and can't do operator overloading, won't you j=
ust have a class with protected methods that are never used and don't ac=
tually do anything?
>=20
> Ah, that could probably be clearer in the RFC, but you have to make it=
 public to be able to use it.

I've iterated it a few times in the text of the RFC.

=E2=80=94 Rob
--72b2bf80d79049289577bf20c409068e
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sun, Ju=
n 30, 2024, at 06:59, Rob Landers wrote:<br></div><blockquote type=3D"ci=
te" id=3D"qt" style=3D""><div><br></div><div><br></div><div>On Sun, Jun =
30, 2024, at 01:28, Saki Takamachi wrote:<br></div><blockquote type=3D"c=
ite" id=3D"qt-qt" style=3D""><div>Hi,<br></div><div><br></div><div>&gt; =
Hello internals,<br></div><div>&gt;&nbsp;<br></div><div>&gt; I've update=
d the RFC to include final-ish examples (barring any further constructiv=
e feedback), a prototype implementation, and an objections section.<br><=
/div><div>&gt;&nbsp;<br></div><div>&gt; Cheers,<br></div><div>&gt;&nbsp;=
<br></div><div>&gt; Rob<br></div><div><br></div><div>It seems like the "=
hack" I mentioned is still possible, am I misunderstanding something?<br=
></div></blockquote><div><br></div><div>That=E2=80=99s always going to b=
e a possibility, no matter what we do or how we do it. I think it would =
be a rather pointless hack now that I can run the code. For the most par=
t, the engine treats these as numbers and trying to dodge that will land=
 you in hot water eventually.&nbsp;<br></div></blockquote><div><br></div=
><div>After playing with the code and seeing what I could get away with,=
 making the GMP class `readonly` appears to prevent many abuses, so I ha=
ve amended the RFC and prototype code.</div><div><br></div><blockquote t=
ype=3D"cite" id=3D"qt" style=3D""><div><br></div><blockquote type=3D"cit=
e" id=3D"qt-qt" style=3D""><div><br></div><div>And I don't understand th=
e purpose of polyfills at all. If you're not using the GMP extensions an=
d can't do operator overloading, won't you just have a class with protec=
ted methods that are never used and don't actually do anything?<br></div=
></blockquote><div><br></div><div>Ah, that could probably be clearer in =
the RFC, but you have to make it public to be able to use it.<br></div><=
/blockquote><div><br></div><div>I've iterated it a few times in the text=
 of the RFC.<br></div><div><br></div><div id=3D"sig121229152">=E2=80=94 =
Rob<br></div></body></html>
--72b2bf80d79049289577bf20c409068e--