Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115815
MIME-Version: 1.0
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
 <df1992f6-fef0-8f62-95d3-dcbc4a5b86d1@gmail.com> <CAF+90c_o1eRxPdJBrOai0Vnmsc=-MYpaWq0wY9zNuL_Vc5jm8Q@mail.gmail.com>
 <763725c0-870b-e8c4-054b-1ea0481ef877@gmail.com> <23055540-3829-6952-5c92-588eb90b699a@processus.org>
In-Reply-To: <23055540-3829-6952-5c92-588eb90b699a@processus.org>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Wed, 25 Aug 2021 08:18:34 -0600
Message-ID: <CAAKU0umrp6vJbRj2R64nyQmp+jqpzMtmSkWG5W5PerBco5Bcdg@mail.gmail.com>
To: Pierre <pierre-php@processus.org>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties
From: internals@lists.php.net ("Levi Morrison via internals")

> And why not adding an extra keyword, such as:
>
> ```
> <?php
> dynamic class Foo { } // Dynamic allowed
> class Bar {} // Dynamic disallowed
> ?>
> ```

I am opposed. IMO it's not worth adding anything to the language to
preserve this existing behavior other than allowing `__get`/`__set`,
etc, which already exist for this purpose.

Additionally, there are technical benefits to removing dynamic
properties altogether, so I don't think we should "half" remove it.
See https://wiki.php.net/rfc/deprecate_dynamic_properties#internal_impact.