On Wed, Oct 23, 2024, at 11:04 AM, ericm...@php.net wrote: > On 10/22/24 22:39, Calvin Buckley wrote: >> After discussing it and thinking about it for a few days, I agree it's >> not a BC break. Existing code should be fine, and larger frameworks >> that tend to rely on reflection trickery and such also tend to need >> updates for newer PHP. The expectations don't really change. >> >> I don't think we need to rush a solution in for 8.4 as long as we can >> implement one with the existing APIs in userland. As Larry mentioned, >> readonly (and hooks) already made the previous assumptions invalid by >> 8.1. As long as we can provide a polyfill and documentation (which >> should also cover the readonly case in 8.1 too), I'm OK with deferring >> isReadable/isWritable to 8.5.
> Chiming in briefly to second Calvin's statement above. > > ~Eric Thanks for the confirmation. We'll work on a small RFC to propose for 8.5. No rush on it. --Larry Garfield
