Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113688 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 93438 invoked from network); 22 Mar 2021 17:21:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Mar 2021 17:21:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B6B86180538 for ; Mon, 22 Mar 2021 10:17:00 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from v-smtpout2.han.skanova.net (v-smtpout2.han.skanova.net [81.236.60.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 22 Mar 2021 10:16:59 -0700 (PDT) Received: from [192.168.7.11] ([213.64.245.126]) by cmsmtp with ESMTPA id OOAjlUTL4jlNVOOAjl2O1D; Mon, 22 Mar 2021 18:16:57 +0100 To: Ben Ramsey References: Cc: PHP internals Message-ID: <52e5a54f-a164-e7bd-f59a-d9b38135998c@telia.com> Date: Mon, 22 Mar 2021 18:16:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: sv Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfDgVldTheGtKnMzHGFUDFY9Qu4To21dYdNftuPylRu1nCozjzyfMM73K+YOfFgHfOqsB6RhwmKLlTIBYxaXrYE+HNfpxLfIb1GK12Le+p32PA6YCwRFK FYRFtu7b9Nu7AB3EdpZffmHqAoyTuImHbUe0ODe9szIVUYttbidSKp8pwhYDcD+qJKrK+c7sxkTgutsrL673hLCx2qHlcdGOCMo= Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.1 From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2021-03-22 kl. 15:58, skrev Ben Ramsey: >> On Mar 22, 2021, at 04:24, Nikita Popov wrote: >> >> Hi internals, >> >> It's time for another deprecation RFC: >> https://wiki.php.net/rfc/deprecations_php_8_1 >> >> This is a collection of minor deprecations that various people have put >> together over the last ~2 years. This RFC was formerly targeted at PHP 8.0, >> but was delayed to PHP 8.1 to reduce the amount of changes necessary for >> PHP 8.0 compatibility. >> >> As usual, each deprecation will be voted in isolation. >> >> As we're still early in the release cycle, it's still possible to add >> additional deprecation candidates, given reasoning for the deprecation, as >> well as available alternatives. >> >> Of course, if there are compelling technical reasons why something should >> not be deprecated, we can move things into the "Removed from this proposal" >> section, in which case it will serve as documentation why some >> functionality should not deprecated. > > > Given Rowan’s thread [1] on `utf8_encode()` and `utf8_decode()`, should we > consider adding these functions to this list or mentioning them in this > RFC as being handled separately? > > Cheers, > Ben > > [1] https://externals.io/message/113645 > In order for that I think a clearer / better motivation is needed. For instance bug reports or community / documented feedback that these functions are giving rise to problems / are misused. Maybe also a checking how frequently thay are used in different Open source libraries. Found several occurences in the Revive ad server. r//Björn L