Re: [RFC] [Vote] PHP 8.3 deprecations
| From: | Björn Larsson via internals | Date: | Thu, 22 Jun 2023 21:24:09 +0000 |
| Subject: | Re: [RFC] [Vote] PHP 8.3 deprecations | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120667@lists.php.net to get a copy of this message | ||
Den 2023-06-22 kl. 14:52, skrev Nicolas Grekas:
better. Hope it will fly! Not sure if this is a relevant comparison, but we have code that we now need to change due to deprecation of utf8_decode and utf8_encode. It is code that has been working flawlessly for 9 years, so it's only work and no benefit. Given that deprecations are piling up for 8.x track I think one should be a bit cautious when approaching the next major version. r//Björn LAs previously announced on the list, we have just started the vote about the annual PHP deprecation RFC. Link to the RFC: https://wiki.php.net/rfc/deprecations_php_8_3 Link to the discussion thread: https://externals.io/message/120422 The vote is open until 2023-07-06 12:00:00 UTC.Thanks Mate for moving all this forward. I wish we could have voted to keep rand() and getrandmax() and just change them to use the CSPRNG, like we do for array_rand() & co. but I guess this should have been proposed earlier. Might be worth a small follow up RFC to not disrupt the current one. Cheers, Nicolas Sounds like a good idea to me, keeping the functions and making them