Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121765
Date: Wed, 22 Nov 2023 22:17:14 +0000
To: PHP Internals <internals@lists.php.net>
User-Agent: K-9 Mail for Android
In-Reply-To: <CAOWwgpnFMtmcojzktbD-P0_rt7tPx8gCcJvku+QYy3io79Oi8g@mail.gmail.com>
References: <2b4591c1-f999-49b5-8061-67db816aa0da@gmail.com> <054a1e3e-f860-4596-83a9-9f557c6fd316@gmail.com> <4c5c9209-e797-49f3-84a8-f8c2371b34d1@app.fastmail.com> <CAOWwgpnFMtmcojzktbD-P0_rt7tPx8gCcJvku+QYy3io79Oi8g@mail.gmail.com>
Message-ID: <DB0E3270-34F3-4248-8B11-2852AC63A595@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 22 November 2023 14:12:09 GMT, Nicolas Grekas <nicolas=2Egrekas+php@gmai=
l=2Ecom> wrote:
>I think there is an inaccuracy that needs to be fixed in the after-unset
>state : as noted later in the RFC, magic accessors are called after an
>unset($this->typedProps)=2E This means the state cannot be described as
>identical ("uninitialized') before and after unset() in the first table i=
n
>the RFC=2E Isn't there some vocabulary in the source that we can use  to
>describe those states more accurately?


Oh=2E Wow=2E That's more than just inaccurate terminology=2E=2E=2E

I always assumed the rule was "access to uninitialised properties triggers=
 __get", not that there was yet another magical state buried in the impleme=
ntation=2E From a user point of view, I find that frankly terrible:

> Typed properties start off as uninitialized, but if you use unset(), you=
 can make them *super-uninitialized*=2E
>
> There's no way to actually see if something's uninitialized or super-uni=
nitialized; and once you've assigned a value, you can't go back to the orig=
inal uninitialized, only to super-uninitialized=2E
>
> Accessing an uninitialized property always throws an error, whereas acce=
ssing a super-uninitialized property will first check for __get=2E

I'm not sure choosing a different name from "super-uninitialized" makes mu=
ch difference to how that reads=2E



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:

> Typed properties start off as uninitialized=2E
>
> Once you've assigned a value, you can't go back to the original uninitia=
lized state using unset()
>
> Accessing an uninitialized property will first check for __get, and thro=
w an error if that isn't defined=2E


Regards,

--=20
Rowan Tommins
[IMSoP]