Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119234
MIME-Version: 1.0
References: <0854b030-c51c-4c1b-a7dd-22835a1e5da9@app.fastmail.com>
 <831b9906-dc0c-420c-b22f-8a0cc8a1ad64@app.fastmail.com> <454c5329-d5a3-5174-d09c-346b7d65435c@bastelstu.be>
 <8f9cf24c-ee77-4227-9b7c-31c631bf8a72@app.fastmail.com> <84647C1B-0F61-41E5-981D-B860BE1E53CB@gmail.com>
 <EB4F7DA5-A526-4E9C-ADF0-31DE86B7368F@gmail.com> <3d8561bd-fdb1-417a-836b-5146fca56185@app.fastmail.com>
 <845495d8-52da-4d2e-90ee-79c697d87f30@app.fastmail.com> <CAPzBOBMgdRU=pWg7A5+rz2tCO3KqB9TVWbOs6fXy4MG9+BqQ_g@mail.gmail.com>
In-Reply-To: <CAPzBOBMgdRU=pWg7A5+rz2tCO3KqB9TVWbOs6fXy4MG9+BqQ_g@mail.gmail.com>
Date: Thu, 5 Jan 2023 20:28:07 +0100
Message-ID: <CAPyj-LAXXwZ-kmvsxwLJOvCOtv+g40LMZdyh5iBnZV=uRrmx1A@mail.gmail.com>
To: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Asymmetric Visibility, with readonly
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Robert

On Thu, Jan 5, 2023 at 3:54 PM Robert Landers <landers.robert@gmail.com> wrote:
>
> One quick question,
>
> Will changing the property of a protected/private set via reflection
> be allowed? Or will you have to do some shenanigans like you currently
> have to do with readonly?

Since PHP 8.1 ReflectionProperty::setValue() allows writing to any
property from any scope by default (assuming it is not readonly)
without calling ReflectionProperty::setAccessible() first.

https://wiki.php.net/rfc/make-reflection-setaccessible-no-op

Essentially, there's no change to the existing behavior. You can write
to an asymmetric property using setValue() just like you could to a
protected or private property as the visibility check is skipped for
these cases.

I added a sentence to the RFCs reflection section to clarify.
Thanks for pointing this out.

Ilija