Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129131
Precedence: list
MIME-Version: 1.0
Date: Fri, 07 Nov 2025 12:03:38 +0100
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] isReadable/isWriteable property reflection
In-Reply-To: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
References: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
Message-ID: <76553cea80282c4b6d71c4ead501415e@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-11-06 00:24, schrieb Larry Garfield:
> 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

I dislike implicitly “scope-dependent” functions, since they effectively 
act like magic. This probably makes it harder to understand for humans 
and static analysis tools alike. I would therefore suggest making the 
`$scope` parameter required. A user can just pass `static::class` 
themselves and static analysis tools can use `class-string|null` instead 
of `class-string|"static"|null` as their expected parameter type.

As for the magic method logic: I would suggest to ignore the presence of 
__get() and __set(). This more closely aligns with the direction PHP 
goes towards and is also easy to work around by checking with 
`method_exists()` whether any such a method exists - the reverse is not 
true.

Best regards
Tim Düsterhus