Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121766
Content-Type: multipart/alternative; boundary=Apple-Mail-1D1D7FBC-FB94-4B4D-8E76-A295B2757260
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
In-Reply-To: <DB0E3270-34F3-4248-8B11-2852AC63A595@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Date: Thu, 23 Nov 2023 02:37:06 +0100
Message-ID: <C2C5C432-B65A-4669-92C5-33A7FD72030B@gmail.com>
References: <DB0E3270-34F3-4248-8B11-2852AC63A595@gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC][Discussion] Harmonise "untyped" and "typed" properties
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail-1D1D7FBC-FB94-4B4D-8E76-A295B2757260
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



> Le 22 nov. 2023 =C3=A0 23:17, Rowan Tommins <rowan.collins@gmail.com> a =C3=
=A9crit :
>=20
> I'm probably going to regret asking this, but is there some reason it work=
s that way? Is there any chance of changing it to just:
>=20
>> Typed properties start off as uninitialized.
>>=20
>> Once you've assigned a value, you can't go back to the original uninitial=
ized state using unset()
>>=20
>> Accessing an uninitialized property will first check for __get, and throw=
 an error if that isn't defined.

Hi Rowan,

What you describe in the last sentence is what was initially designed and im=
plemented by the RFC: https://wiki.php.net/rfc/typed_properties_v2 (section O=
verloaded Properties).

However, it was later changed to the current semantics (unset() needed in or=
der to trigger __get()) in https://github.com/php/php-src/pull/4974

=E2=80=94Claude=

--Apple-Mail-1D1D7FBC-FB94-4B4D-8E76-A295B2757260--