Re: [RFC] isReadable/isWriteable property reflection

From: Date: Wed, 17 Dec 2025 18:02:39 +0000
Subject: Re: [RFC] isReadable/isWriteable property reflection
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-129638@lists.php.net to get a copy of this message
Hi Am 2025-12-17 16:26, schrieb Larry Garfield:
* 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.
That works for me. I didn't feel particularly strongly either way.
We consider the RFC feature complete at this point. Baring any further substantive discussion, expect a vote in January after the blackout period ends.
I don't have further comments about the semantics themselves, but have one further clarification question:
The property has not been unset(). If it has, follow the same __isset check as above
Should this read “the same __get check” instead? And one note with regard to process: Don't forget to add a link to the discussion (https://news-web.php.net/php.internals/129101) to the RFC. Best regards Tim Düsterhus

« previous php.internals (#129638) next »