Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode
| From: | Craig Francis | Date: | Sun, 20 Feb 2022 21:24:19 +0000 |
| Subject: | Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117081@lists.php.net to get a copy of this message | ||
On Sun, 20 Feb 2022 at 18:55, Rowan Tommins <rowan.collins@gmail.com> 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
>
Thanks Rowan.
Whenever I see these functions being used (including when I used them),
it's been, as you note, "commonly misunderstood" - so I'd be happy to see
the back of them.
Only query I have is about the availability of different functions... not
sure why, but the documentation says these are provided by the
"xml" extension, even though it looks like they are in
./standard/string.c (your pull request seems to correct this)... so I
assume projects have used these functions on the basis that they are always
available... I suppose you could argue that "iconv" is enabled by default,
so that's hopefully reliable (even though it can be disabled with
--without-iconv)... whereas "mbstring" and "intl" are non-default
extensions.
Craig