Re: [VOTE] Deprecate dynamic properties
| From: | Larry Garfield | Date: | Tue, 16 Nov 2021 16:35:21 +0000 |
| Subject: | Re: [VOTE] Deprecate dynamic properties | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-116418@lists.php.net to get a copy of this message | ||
On Tue, Nov 16, 2021, at 7:18 AM, Lynn wrote:
> On Tue, Nov 16, 2021 at 1:23 PM Pierre Joye <pierre.php@gmail.com> wrote:
>
>> On Tue, Nov 16, 2021 at 4:11 PM Lynn <kjarli@gmail.com> wrote:
>> > What is the point of this change if it's an opt-in? Projects that are
>> still relying on dynamic properties today and "have no time" to fix them
>> now, won't have time in 3 years either. Please let us have nice things
>> today instead of years from now :)
>>
>> If it is an opt-in (like Larry proposes f.e.), you will have them
>> today as well.
>>
>>
> Just to be clear, are you talking about opting in to having the
> deprecation, thus adding it to every single class in my code base, and
> every new class added in the future? Or are you talking about opting in to
> enabling dynamic properties? Because the first makes it pointless to have
> while the latter makes this a great RFC.
I believe Pierre is referring to my suggestion here: https://externals.io/message/115800#116382
--Larry Garfield