Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117484
MIME-Version: 1.0
References: <624d81b4.1c69fb81.eae57.b277SMTPIN_ADDED_MISSING@mx.google.com> <CAPzBOBMAUGHKkN1gFVYPUiMbNGz7Ni+u7tdS+EB2M-axugVvzg@mail.gmail.com>
In-Reply-To: <CAPzBOBMAUGHKkN1gFVYPUiMbNGz7Ni+u7tdS+EB2M-axugVvzg@mail.gmail.com>
Date: Wed, 6 Apr 2022 15:36:47 +0200
Message-ID: <CAC5V6ggKqX0pCDjD3BKsuj78bBNEV_CvegZnoZ-uLCSiYCn67Q@mail.gmail.com>
To: Robert Landers <landers.robert@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a5d37305dbfc7438"
Subject: Re: [PHP-DEV] [RFC] Undefined Property Error Promotion
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--000000000000a5d37305dbfc7438
Content-Type: text/plain; charset="UTF-8"

On Wed, Apr 6, 2022 at 2:37 PM Robert Landers <landers.robert@gmail.com>
wrote:

>
> FWIW, I'd like to see option 2 only because of custom serializers
> and/or object proxies and also because:
>
> > This RFC proposes that accessing an undefined property is rendered
> illegal behaviour
>
> StdClass has *no* defined properties and thus would always throw. But
> I also guess it depends on what you define "undefined" as. Does simply
> doing $obj->prop "define" the property "prop"?
>

The RFC doesn't change the current meaning of "undefined" (or "defined", or
"declared"...), just proposes to throw an Error (while it currently
triggers an E_WARNING).
First sentence of the introduction: "Undefined properties are those that
have not yet been defined either by the presence of a property declaration,
or by adding them to the properties hashmap through direct assignment, or
by having them assigned by an internal function such as json_decode."
`$obj->prop` alone doesn't define the property "prop", but `$obj->prop =
whatever` does.

Regards,

-- 
Guilliam Xavier

--000000000000a5d37305dbfc7438--