Re: Please allow an out of readonly properties
| From: | Karoly Negyesi | Date: | Sat, 03 Dec 2022 22:45:43 +0000 |
| Subject: | Re: Please allow an out of readonly properties | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119081@lists.php.net to get a copy of this message | ||
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
>>
>