Re: [RFC] isReadable/isWriteable property reflection
| From: | Nicolas Grekas | Date: | Wed, 17 Dec 2025 20:33:23 +0000 |
| Subject: | Re: [RFC] isReadable/isWriteable property reflection | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129645@lists.php.net to get a copy of this message | ||
Le mer. 17 déc. 2025 à 16:29, Larry Garfield <larry@garfieldtech.com> a
écrit :
> 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() implies
> 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 period
> ends.
>
Hi, thanks for the update!
I read the updated description and that looks great to me, thanks.
Nicolas