Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124082
Content-Type: multipart/alternative; boundary=Apple-Mail-D0D6DF18-BFEE-4987-852F-9733DBBDA570
Content-Transfer-Encoding: 7bit
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] Operator Overrides -- Lite Edition
In-Reply-To: <466994ae-64b0-4c73-a841-31de082ed247@app.fastmail.com>
Cc: "Gina P. Banyard" <internals@gpb.moe>, internals@lists.php.net
Date: Sun, 30 Jun 2024 20:05:02 +0900
Message-ID: <EE1978EA-E916-4884-9633-9578AE67D436@sakiot.com>
References: <466994ae-64b0-4c73-a841-31de082ed247@app.fastmail.com>
To: Rob Landers <rob@bottled.codes>
From: saki@sakiot.com (Saki Takamachi)


--Apple-Mail-D0D6DF18-BFEE-4987-852F-9733DBBDA570
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi,

>> I'm not sure. Does this mean that such "hack" is unavoidable?
>>=20
>> And I don't really understand what "pointless hack" means. This would mak=
e sense if operator overloading was already allowed, but it isn't.
>=20
> Not unavoidable, but pointless. For example, I attempted to create a Strin=
g class that used + for concatenation. This kinda works, but if you pass it t=
o something that takes a string, you get the underlying number and not the s=
tring you were trying to store. This is because GMP takes over casting forci=
ng you to stick to numerical constructs.

I don't understand why you only consider the casting case. You can simply co=
nvert it to a string via a method. As long as don't use any casting at the e=
nd, users can implement it however they like. I don't think this is a pointl=
ess hack.

Also, allowing "hack" just because they're not useful is not a good idea.

Again, if such functionality is provided, it should be exposed as formal sup=
port for operator overloading.

>> This is very confusing me. Why does this need to be a child class of GMP?=

>=20
> This is addressed in the current RFC text, if I missed something, please a=
sk!

I don't understand why the GMP RFC mentions environments where GMP is not us=
ed.

There are a few other points worth mentioning, but the existence of polyfill=
s makes this especially confusing.

> To be usable, the developer must override the desired operations and make t=
hem public

Is this referring to a polyfill? Or is this just a necessary step to overrid=
e the overload?

Regards,

Saki=

--Apple-Mail-D0D6DF18-BFEE-4987-852F-9733DBBDA570
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"><meta http-equiv=3D"conten=
t-type" content=3D"text/html; charset=3Dutf-8"><div dir=3D"ltr"><meta http-e=
quiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div dir=3D"ltr=
"></div><div dir=3D"ltr">Hi,</div><div dir=3D"ltr"><br></div><blockquote typ=
e=3D"cite"><div dir=3D"ltr"><blockquote type=3D"cite" id=3D"qt" style=3D""><=
div>I'm not sure. Does this mean that such "hack" is unavoidable?<br></div><=
div><br></div><div>And I don't really understand what "pointless hack" means=
. This would make sense if operator overloading was already allowed, but it i=
sn't.<br></div></blockquote><div><br></div><div>Not unavoidable, but pointle=
ss. For example, I attempted to create a String class that used + for concat=
enation. This kinda works, but if you pass it to something that takes a stri=
ng, you get the underlying number and not the string you were trying to stor=
e. This is because GMP takes over casting forcing you to stick to numerical c=
onstructs.</div></div></blockquote><div><br></div><div>I don't understand wh=
y you only consider the casting case. You can simply convert it to a string v=
ia a method. As long as don't use any casting at the end, users can implemen=
t it however they like. I don't think this is a pointless hack.</div><div><b=
r></div><div>Also, allowing "hack" just because they're not useful is not a g=
ood idea.</div><div><br></div><div>Again, if such functionality is provided,=
 it should be exposed as formal support for operator overloading.</div><div>=
<br></div><blockquote type=3D"cite"><div dir=3D"ltr"><blockquote type=3D"cit=
e" id=3D"qt" style=3D""><div>This is very confusing me. Why does this need t=
o be a child class of GMP?<br></div></blockquote><div><br></div><div>This is=
 addressed in the current RFC text, if I missed something, please ask!</div>=
</div></blockquote><br><div>I don't understand why the GMP RFC mentions envi=
ronments where GMP is not used.</div><div><br></div><div>There are a few oth=
er points worth mentioning, but the existence of polyfills makes this especi=
ally confusing.</div><div><br></div><div>&gt;&nbsp;<span style=3D"caret-colo=
r: rgb(51, 51, 51); color: rgb(51, 51, 51); font-family: &quot;Fira Sans&quo=
t;, &quot;Source Sans Pro&quot;, Helvetica, Arial, sans-serif; font-size: 16=
px; -webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">T=
o be usable, the developer must override the desired operations and make the=
m public</span></div><div><span style=3D"caret-color: rgb(51, 51, 51); color=
: rgb(51, 51, 51); font-family: &quot;Fira Sans&quot;, &quot;Source Sans Pro=
&quot;, Helvetica, Arial, sans-serif; font-size: 16px; -webkit-text-size-adj=
ust: auto; background-color: rgb(255, 255, 255);"><br></span></div><div>Is t=
his referring to a polyfill? Or is this just a necessary step to override th=
e overload?</div><div><br></div><div>Regards,</div><div><br></div><div>Saki<=
/div></div></div></body></html>=

--Apple-Mail-D0D6DF18-BFEE-4987-852F-9733DBBDA570--