Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129633
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Wed, 17 Dec 2025 09:26:23 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <09b0365c-9708-4c38-8004-5b1ca693ad8c@app.fastmail.com>
In-Reply-To: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
References: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
Subject: Re: [PHP-DEV] [RFC] isReadable/isWriteable property reflection
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

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.

--Larry Garfield