Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117409
To: internals@lists.php.net
References: <22242169-a16d-5261-696c-3cf00b00336a@gmail.com>
 <0b322a3e-469a-7ed7-16e3-0b76287f4091@gmail.com>
Message-ID: <623BAFB6.4000901@adviesenzo.nl>
Date: Thu, 24 Mar 2022 00:39:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <0b322a3e-469a-7ed7-16e3-0b76287f4091@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------080607030608020705090909"
Subject: Re: ***SPAM*** [PHP-DEV] Re: [RFC] Deprecate and Remove utf8_encode
 and utf8_decode
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

--------------080607030608020705090909
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 23-3-2022 14:46, Rowan Tommins wrote:
> On 20/02/2022 18:55, Rowan Tommins wrote:
>>
>> I would like to open discussion on an RFC to deprecate and later 
>> remove the functions utf8_encode() and utf8_decode()
>>
>> https://wiki.php.net/rfc/remove_utf8_decode_and_utf8_encode
>
>
> Final chance for feedback on this RFC, as revised, before I put it to 
> a vote.
>
> There's been very little reaction on this thread, which I'm hoping 
> means everyone's either planning to vote "Yes" or just doesn't care...
>
> Regards,
>

While I agree the functions are often used incorrectly, what worries me 
about this RFC is that the only viable alternatives for these functions 
are in two optional extensions, which in practice will mean lots of 
projects will need to start polyfilling the old functions and/or start 
including a polyfill for one of the extensions, as they can not rely on 
those optional extensions being turned on.

--------------080607030608020705090909--