Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115895
Date: Mon, 30 Aug 2021 14:13:42 +0200
To: internals@lists.php.net
Message-ID: <20210830141342.2077bcfb@mcmic-probook.opensides.be>
In-Reply-To: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
Organization: FusionDirectory
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties
From: come.chilliet@fusiondirectory.org (=?UTF-8?B?Q8O0bWU=?= Chilliet)

Le Wed, 25 Aug 2021 12:02:49 +0200,
Nikita Popov <nikita.ppv@gmail.com> a =C3=A9crit :
> Hi internals,
>=20
> I'd like to propose the deprecation of "dynamic properties", that is
> properties that have not been declared in the class (stdClass and
> __get/__set excluded, of course):
>=20
> https://wiki.php.net/rfc/deprecate_dynamic_properties

If I understand correctly the RFC, in these two classes:

class A {
    public $prop;
=20
    public function __construct() {
        unset($this->prop);
    }
}

class B {
    public $prop;
}

The property $prop is not in the same state in the end? What is the differe=
nce?
isset returns FALSE for both, no? And property_exists?

Is it something that was the same before the RFC and would be different aft=
er,
or is it already two different cases and how?

C=C3=B4me