Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128130
Content-Type: multipart/alternative; boundary=Apple-Mail-FF1AA0CA-4419-4D7C-BDDA-0C0CB33137FA
Content-Transfer-Encoding: 7bit
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] Re: [RFC] Readonly property hooks
In-Reply-To: <378cd8b0-c4a8-4e53-b0bd-e9e4f30a454d@app.fastmail.com>
Cc: erictnorris@gmail.com, Nicolas Grekas <nicolas.grekas+php@gmail.com>,
 Larry Garfield <larry@garfieldtech.com>,
 =?utf-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>,
 php internals <internals@lists.php.net>
Date: Sat, 19 Jul 2025 03:04:08 +0200
Message-ID: <77128196-8D53-40D6-9BB7-77160AD71ED9@gmail.com>
References: <378cd8b0-c4a8-4e53-b0bd-e9e4f30a454d@app.fastmail.com>
To: Rob Landers <rob@bottled.codes>
From: claude.pache@gmail.com (Claude Pache)


--Apple-Mail-FF1AA0CA-4419-4D7C-BDDA-0C0CB33137FA
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



> Le 19 juil. 2025 =C3=A0 00:41, Rob Landers <rob@bottled.codes> a =C3=A9cri=
t :
>=20
> The original author (Nikita) suggested that there's nothing in the origina=
l design that precludes accessors -- and highlights languages where there ar=
e both and they are doing just fine more than 5 years later.

Hi Rob,

It is indeed entirely reasonable to have both readonly properties and hooked=
 properties (aka accessors), and today PHP has indeed both of them (and even=
 asymmetric visibility on top of that, as a separate feature contrarily to C=
#). But it doesn=E2=80=99t mean that it is reasonable for the *same* propert=
y to be *both* readonly and hooked, which is the point that is currently dis=
puted. =E2=80=94 What do the other languages allow? Is it possible to define=
 a readonly property with a user-defined getter? (Disclaimer: Even if one of=
 them allows such a thing, I=E2=80=99ll still think that it is a bad idea.)

=E2=80=94Claude=20=

--Apple-Mail-FF1AA0CA-4419-4D7C-BDDA-0C0CB33137FA
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"></div><div d=
ir=3D"ltr"><br></div><div dir=3D"ltr"><br><blockquote type=3D"cite">Le 19 ju=
il. 2025 =C3=A0 00:41, Rob Landers &lt;rob@bottled.codes&gt; a =C3=A9crit&nb=
sp;:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr"><d=
iv class=3D"align-start" style=3D"text-align:start;"><br></div><div class=3D=
"align-start" style=3D"text-align:start;">The original author (Nikita) sugge=
sted that there's nothing in the original design that precludes accessors --=
 and highlights languages where there are both and they are doing just fine m=
ore than 5 years later.</div><div class=3D"align-start" style=3D"text-align:=
start;"></div></div></blockquote><br><div>Hi Rob,</div><div><br></div><div>I=
t is indeed entirely reasonable to have both readonly properties and hooked p=
roperties (aka accessors), and today PHP has indeed both of them (and even a=
symmetric visibility on top of that, as a separate feature contrarily to C#)=
. But it doesn=E2=80=99t mean that it is reasonable for the *same* property t=
o be *both* readonly and hooked, which is the point that is currently disput=
ed. =E2=80=94 What do the other languages allow? Is it possible to define a r=
eadonly property with a user-defined getter? (Disclaimer: Even if one of the=
m allows such a thing, I=E2=80=99ll still think that it is a bad idea.)</div=
><div><br></div><div>=E2=80=94Claude&nbsp;</div></div></body></html>=

--Apple-Mail-FF1AA0CA-4419-4D7C-BDDA-0C0CB33137FA--