Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95315
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXYGUhihdbMMBQB7FQ6CnmYqrB_x2YVjdZTvT8gDs59oOQ@mail.gmail.com>
References: <CAGa2bXYGUhihdbMMBQB7FQ6CnmYqrB_x2YVjdZTvT8gDs59oOQ@mail.gmail.com>
Date: Fri, 19 Aug 2016 22:12:05 +0700
Message-ID: <CAEZPtU7Zq=RpNMYz6dRCaiUVLFf4S68MOQHxPFVBsWaRZu9cJQ@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113adc3e2ae183053a6e1f3f
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Remove utf8_decode() and utf8_encode()
From: pierre.php@gmail.com (Pierre Joye)

--001a113adc3e2ae183053a6e1f3f
Content-Type: text/plain; charset=UTF-8

On Aug 15, 2016 10:18 AM, "Yasuo Ohgaki" <yohgaki@ohgaki.net> wrote:
>
> Hi all,
>
> utf8_decode() and utf8_encode() are not needed and causing problems
> than solving.
>
> https://wiki.php.net/rfc/remove_utf_8_decode_encode
>
> Proposal
>   - Document deprecation them now
>   - Remove them from 7.2
>
> I think only few users are using and they shouldn't have problem using
> mbstring/iconv/intl functions.
>
> Any comments?

Yes, one, sadly short:

Absolutely no go.

I do not see a remotely valid reason to remove these functions which are
much more used than what this RFC or thread say.

I am against removing them, now or in 8.x. this is the kind of things that
makes migrations painful. They are broken on some cases? Fix them maybe?

--001a113adc3e2ae183053a6e1f3f--