Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116264
MIME-Version: 1.0
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
 <CAF+90c-jw48ymXvO34E+oVua6_FV0NhwE_jnPgBZ=LurthnKeA@mail.gmail.com>
In-Reply-To: <CAF+90c-jw48ymXvO34E+oVua6_FV0NhwE_jnPgBZ=LurthnKeA@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Tue, 12 Oct 2021 07:52:42 -0600
Message-ID: <CAAKU0u=qmrJ4TAxDH1v394nWJwYpJqKB7YXN-wabPrGBKZtEjw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Re: [RFC] Deprecate dynamic properties
From: internals@lists.php.net ("Levi Morrison via internals")

> Based on the received feedback, I've updated the RFC to instead provide an
> #[AllowDynamicProperties] attribute as a way to opt-in to the use of
> dynamic properties. As previously discussed, this won't allow us to
> completely remove dynamic properties from the language model anymore, but
> it will make the upgrade path smoother by avoiding multiple inheritance
> issues.

Quoting the updated RFC:
> We may still wish to remove dynamic properties entirely at some later
> point. Having the #[AllowDynamicProperties] attribute will make it much
> easier to evaluate such a move, as it will be easier to analyze how much
> and in what way dynamic properties are used in the ecosystem.

But in this place it does not mention PHP 9.0. Other places still
mention converting it to an error for PHP 9.0. Is that still the plan?