Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129547
Precedence: list
MIME-Version: 1.0
References: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
In-Reply-To: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
Date: Thu, 4 Dec 2025 15:05:47 +0100
Message-ID: <CAOWwgp=L=YaZDdLmFr+paOVEotU1Lt6S4vAuU+HFTNAo0S0hSQ@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="000000000000194e5e064520d401"
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000194e5e064520d401
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le jeu. 6 nov. 2025 =C3=A0 00:28, Larry Garfield <larry@garfieldtech.com> a
=C3=A9crit :

> 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 whil=
e,
> but here we are.  A strangely small RFC from us:
>
> https://wiki.php.net/rfc/isreadable-iswriteable
>
>

Thanks for this.
I also think the auto-scope is a good idea. You state that 90% of use cases
will need this but my experience doesn't back this claim. The only cases
where I had to check for read/writeable were out of the local scope, so I'd
say 100% of my experience goes against that 90% number ;) Joke aside, it'd
be just fine to let ppl be explicit. That's better than "oops I forgot to
give the correct scope" bugs.

About magic methods, one unsets a property only to have __get/__set called.
Existing code works with this assumption. This means we have to return true
IMHO. Magic methods are just generic hooks also. Which means they should
behave the same.

Nicolas

--000000000000194e5e064520d401
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0jeu. 6 nov.=
 2025 =C3=A0=C2=A000:28, Larry Garfield &lt;<a href=3D"mailto:larry@garfiel=
dtech.com">larry@garfieldtech.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">In other news, Ilija and I sa=
id a year ago that we&#39;d take a swing at adding isReadable/isWriteable m=
ethods to ReflectionProperty.=C2=A0 Took a while, but here we are.=C2=A0 A =
strangely small RFC from us:<br>
<br>
<a href=3D"https://wiki.php.net/rfc/isreadable-iswriteable" rel=3D"noreferr=
er" target=3D"_blank">https://wiki.php.net/rfc/isreadable-iswriteable</a><b=
r>
<br></blockquote><div><br></div><div><br></div>Thanks for this.<br class=3D=
"gmail-Apple-interchange-newline"><div>I also think the auto-scope is a goo=
d idea. You state that 90% of use cases will need this but my experience do=
esn&#39;t back this claim. The only cases where I had to check for read/wri=
teable=C2=A0were out of the local scope, so I&#39;d say 100% of my experien=
ce goes against that 90% number ;) Joke aside, it&#39;d be just fine to let=
 ppl be explicit. That&#39;s better than &quot;oops I forgot to give the co=
rrect scope&quot; bugs.</div><div><br></div><div>About magic methods, one u=
nsets a property=C2=A0only to have __get/__set called. Existing code works =
with this assumption. This means we have to return true IMHO. Magic methods=
 are just generic hooks also. Which means they should behave the same.</div=
><div><br></div><div>Nicolas</div></div></div>

--000000000000194e5e064520d401--