Re: [VOTE] Deprecate dynamic properties
| From: | Tobias Nyholm | Date: | Wed, 17 Nov 2021 00:29:45 +0000 |
| Subject: | Re: [VOTE] Deprecate dynamic properties | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-116432@lists.php.net to get a copy of this message | ||
Thank you Sara!
I could not agree more with you. I think this answers to most tweets and messages that I’ve seen
the past few weeks.
// Tobias
> On 16 Nov 2021, at 14:20, Sara Golemon <pollita@php.net> wrote:
>
> Serious questions for all the folks worried that this is some kind of death
> nail for PHP.
>
> 1. Do you have code you're responsible for which uses dynamic properties so
> broadly that adding this attribute is a burden?
> 2. Do you know of real code in widespread use which uses dynamic properties
> so broadly that adding this attribute is a burden?
>
> All I see being bandied about are hypotheticals. So here's my answers: In
> my entire career (which granted, is only about half actually written IN
> php) I can point to exactly one class* which makes use of dynamic props and
> it would take me a hot minute to add the attribute and commit it to the
> repo (note: This code base is running on 5.x, so it doesn't need it, but it
> can handle the attribute all the same). I don't consider that hot minute
> to be problematic.
>
> For those wondering what's the point: Making the engine better is the
> point. We won't see the payoff in 8.2, or even 9.0, but by 10.0 we should
> be able to be in a better place and have a better engine out of it.
>
> -Sara
>
> * Not counting uses of stdClass which is going to implicitly have this
> attribute.