Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129645
Precedence: list
MIME-Version: 1.0
References: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com> <09b0365c-9708-4c38-8004-5b1ca693ad8c@app.fastmail.com>
In-Reply-To: <09b0365c-9708-4c38-8004-5b1ca693ad8c@app.fastmail.com>
Date: Wed, 17 Dec 2025 21:33:23 +0100
Message-ID: <CAOWwgpmnwb4Tu+sVLuTeyeAX1V65hCEo9UCTV1W4WYpM8CBcKg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] isReadable/isWriteable property reflection
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001597eb06462bc247"
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000001597eb06462bc247
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le mer. 17 d=C3=A9c. 2025 =C3=A0 16:29, Larry Garfield <larry@garfieldtech.=
com> a
=C3=A9crit :

> On Wed, Nov 5, 2025, at 5:24 PM, Larry Garfield wrote:
> > In other news, Ilija and I said a year ago that we'd take a swing at
> > adding isReadable/isWriteable methods to ReflectionProperty.  Took a
> > while, but here we are.  A strangely small RFC from us:
> >
> > https://wiki.php.net/rfc/isreadable-iswriteable
>
> A few updates based on the discussion here:
>
> * We now account for static properties.  (What a concept.)
> * The `static` magic string is gone.
> * We have decided on an approach for magic methods.  The updated RFC text
> explains it in more detail, but in short, "if __isset(), then use that to
> determine readable.  Otherwise, __get() implies readable.  __set() implie=
s
> writeable."  That should handle the use cases Nicolas was interested in.
>
> We consider the RFC feature complete at this point.  Baring any further
> substantive discussion, expect a vote in January after the blackout perio=
d
> ends.
>

Hi, thanks for the update!
I read the updated description and that looks great to me, thanks.

Nicolas

--0000000000001597eb06462bc247
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0mer. 17=
 d=C3=A9c. 2025 =C3=A0=C2=A016:29, Larry Garfield &lt;<a href=3D"mailto:lar=
ry@garfieldtech.com">larry@garfieldtech.com</a>&gt; a =C3=A9crit=C2=A0:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Nov 5, 2025=
, at 5:24 PM, Larry Garfield wrote:<br>
&gt; In other news, Ilija and I said a year ago that we&#39;d take a swing =
at <br>
&gt; adding isReadable/isWriteable methods to ReflectionProperty.=C2=A0 Too=
k a <br>
&gt; while, but here we are.=C2=A0 A strangely small RFC from us:<br>
&gt;<br>
&gt; <a href=3D"https://wiki.php.net/rfc/isreadable-iswriteable" rel=3D"nor=
eferrer" target=3D"_blank">https://wiki.php.net/rfc/isreadable-iswriteable<=
/a><br>
<br>
A few updates based on the discussion here:<br>
<br>
* We now account for static properties.=C2=A0 (What a concept.)<br>
* The `static` magic string is gone.<br>
* We have decided on an approach for magic methods.=C2=A0 The updated RFC t=
ext explains it in more detail, but in short, &quot;if __isset(), then use =
that to determine readable.=C2=A0 Otherwise, __get() implies readable.=C2=
=A0 __set() implies writeable.&quot;=C2=A0 That should handle the use cases=
 Nicolas was interested in.<br>
<br>
We consider the RFC feature complete at this point.=C2=A0 Baring any furthe=
r substantive discussion, expect a vote in January after the blackout perio=
d ends.<br></blockquote><div><br></div><div>Hi, thanks for the update!</div=
><div>I read the updated description and that looks great to=C2=A0me, thank=
s.</div><div><br></div><div>Nicolas</div></div></div>

--0000000000001597eb06462bc247--