Re: [RFC] Deprecations for PHP 8.4
| From: | Morgan | Date: | Wed, 26 Jun 2024 19:19:27 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 8.4 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-123882@lists.php.net to get a copy of this message | ||
I do not believe it is appropriate to deprecate strtok() without a proper
replacement.
While I agree that its signature is undesirable, the suggested replacement
functions or “just write a parser” are not very pleasant solutions to fill
the void it would leave.
The stateful functionality it exhibits is incredibly useful, though I will
admit confusing. Would it not be better to change how the functionality is
accessed to reflect the fact that state is preserved rather than remove it
entirely and force a performance burden on developers?
On Tue, Jun 25, 2024 at 10:38 AM Gina P. Banyard <internals@gpb.moe> wrote:
> Hello internals,
>
> It is this time of year again where we proposed a list of deprecations to
> add in PHP 8.4:
>
> https://wiki.php.net/rfc/deprecations_php_8_4
>
> As a reminder, this list has been compiled over the course of the past
> year by various different people.
>
> And as usual, each deprecation will be voted in isolation.
>
> We still have a bit of time buffer, so if anyone else has any suggestions,
> they are free to add them to the RFC.
>
> Some should be non-controversial, others a bit more.
> If such, they might warrant their own dedicated RFC, or be dropped from
> the proposal altogether.
>
>
> Best regards,
>
> Gina P. Banyard
>