Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108681
MIME-Version: 1.0
References: <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
In-Reply-To: <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
Date: Wed, 19 Feb 2020 18:52:02 +0100
Message-ID: <CADyq6sL4-ef_5O+uU4ucnym1YVQe=BVT5ZWRy=qenAOw0-e=xw@mail.gmail.com>
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c7c81f059ef172b7"
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Immutable/final/readonly properties
From: ocramius@gmail.com (Marco Pivetta)

--000000000000c7c81f059ef172b7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Mark,

Asking here as well, so that others are aware: is
`unset($this->aPropertyThatWasNotInitializedBefore)` still working with
this patch?

Also, are the semantics around `__get`, `__set` and `__isset` the same as
with typed properties?

In the RFC, you have `unset($foo->c)` as disallowed: the property isn't
declared nor initialized though. I'd expect this to fail only after first
initialization?

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Wed, Feb 19, 2020 at 6:06 PM M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.c=
om> wrote:

> Hi Internals,
>
> I'd like to move my RFC forward to the discussion phase:
> https://wiki.php.net/rfc/write_once_properties
>
> In short, I propose to add support for a new property modifier that would
> allow properties to be initialized, but not modified afterwards.
>
> Cheers,
> M=C3=A1t=C3=A9 Kocsis
>

--000000000000c7c81f059ef172b7--