Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119081
MIME-Version: 1.0
References: <CAOfzkkyqi0YRt1gycozdsO+pBVX9WForw-a=+GAKFyGSGOg9rg@mail.gmail.com>
 <CADyq6sJVga_Bvm54BNPj3tQ1iiqJzoVeDj8AL3esoHuSmKFgXg@mail.gmail.com>
In-Reply-To: <CADyq6sJVga_Bvm54BNPj3tQ1iiqJzoVeDj8AL3esoHuSmKFgXg@mail.gmail.com>
Date: Sat, 3 Dec 2022 14:45:43 -0800
Message-ID: <CAOfzkkzCj7DpTj9BObr6Am=PENyPJ=tq-yMwAgUNxTDBRPEymQ@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000784fbb05eef43719"
Subject: Re: [PHP-DEV] Please allow an out of readonly properties
From: karoly@negyesi.net (Karoly Negyesi)

--000000000000784fbb05eef43719
Content-Type: text/plain; charset="UTF-8"

I do not have the luxury of designing my own system. I am forced to use
upstream. I can't help it and given the history of private usage and the
refusal on relaxing them I do not see this improving with the readonly. At
all.

On Sat, Dec 3, 2022 at 2:42 PM Marco Pivetta <ocramius@gmail.com> wrote:

> Terrible idea: reflection is mostly introspection tooling, and doesn't
> really bend the rules of the type system, other than crossing scope (it
> "sees" more).
>
> Please consider designing your system to consider the constraints of
> `readonly` properties, or design the constraints to fit your system instead.
>
> Marco Pivetta
>
> https://twitter.com/Ocramius
>
> https://ocramius.github.io/
>
>
> On Sat, 3 Dec 2022 at 23:39, Karoly Negyesi <karoly@negyesi.net> wrote:
>
>> Hello,
>>
>> If push comes to shove, private properties can be changed with reflection.
>>
>> Readonly properties can't.
>>
>> Please add a readonly toggle to reflection.
>>
>> Thanks
>>
>> Karoly Negyesi
>>
>

--000000000000784fbb05eef43719--