Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121770
Date: Thu, 23 Nov 2023 07:56:07 +0000
CC: PHP Internals <internals@lists.php.net>
User-Agent: K-9 Mail for Android
In-Reply-To: <C2C5C432-B65A-4669-92C5-33A7FD72030B@gmail.com>
References: <DB0E3270-34F3-4248-8B11-2852AC63A595@gmail.com> <C2C5C432-B65A-4669-92C5-33A7FD72030B@gmail.com>
Message-ID: <EFC20C43-EFD2-44F0-B4A9-47AA7E6D8824@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: =?US-ASCII?Q?Re=3A_=5BPHP-DEV=5D_Re=3A_=5BRFC=5D=5BDiscussion=5D_Har?= =?US-ASCII?Q?monise_=22untyped=22_and_=22typed=22_properties?=
From: rowan.collins@gmail.com (Rowan Tommins)

On 23 November 2023 01:37:06 GMT, Claude Pache <claude=2Epache@gmail=2Ecom>=
 wrote:
>What you describe in the last sentence is what was initially designed and=
 implemented by the RFC: https://wiki=2Ephp=2Enet/rfc/typed_properties_v2 (=
section Overloaded Properties)=2E
>
>However, it was later changed to the current semantics (unset() needed in=
 order to trigger __get()) in https://github=2Ecom/php/php-src/pull/4974


Good find=2E So not only is it not specified this way in the RFC, it actua=
lly made it into a live release, then someone complained and we rushed out =
a more complicated version "to avoid WTF"=2E That's really unfortunate=2E

I'm not at all convinced by the argument in the linked bug report - whethe=
r you get an error or an unexpected call to __get, the solution is to assig=
n a valid value to the property=2E And making the behaviour different after=
 unset() just hides the user's problem, which is that they didn't expect to=
 *ever* have a call to __get for that property=2E

But I guess I'm 4 years too late to make that case=2E

Regards,

--=20
Rowan Tommins
[IMSoP]