Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120667 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 4403 invoked from network); 22 Jun 2023 21:24:10 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 22 Jun 2023 21:24:10 -0000 To: internals@lists.php.net,Nicolas Grekas Message-ID: Date: Thu, 22 Jun 2023 23:24:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 References: Content-Language: en-GB, sv Reply-To: =?UTF-8?Q?Bj=c3=b6rn_Larsson?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 84.216.97.240 Subject: Re: [PHP-DEV] [RFC] [Vote] PHP 8.3 deprecations From: internals@lists.php.net ("Björn Larsson via internals") Den 2023-06-22 kl. 14:52, skrev Nicolas Grekas: >> >> As 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 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 L