Re: [RFC] [Discussion] Deprecate functions with overloaded signatures
| From: | Dan Ackroyd | Date: | Thu, 11 May 2023 16:58:26 +0000 |
| Subject: | Re: [RFC] [Discussion] Deprecate functions with overloaded signatures | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120234@lists.php.net to get a copy of this message | ||
On Thu, 11 May 2023 at 10:36, Tim Düsterhus <tim@bastelstu.be> wrote:
>
> Would it be an option to just deprecate everything in PHP 8.3
As I said before, having at least one version where the new versions
of the functions are available, and the old versions aren't giving
deprecation notices, is the 'cleanest' way of refactoring functions.
Deprecation notices only deliver their value when the old versions of
the functions are removed, and before then are a cost.
> It doesn't really feel right to decide on
> a deprecation for 9.0 / removal for 10.0 at the current time, but
> deprecation in 8.3 + removal when it's ready seems to be okay.
I think I don't understand your concern.
If a problem is discovered with a planned removal of something, people
on this project are mostly reasonable*, and a small RFC to adjust to
the new circumstances would be very likely to pass.
cheers
Dan
Ack
* though sometimes they base their decisions on experiences/value
different from my own, which makes it not feel like that.