Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96749
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52157a07-edf4-5c43-4abc-4cf2f3d869ee@php.net>
References: <cdd4edeaf066e73ca2ebdede5d5c535b@pmmaga.net> <52157a07-edf4-5c43-4abc-4cf2f3d869ee@php.net>
Date: Sun, 6 Nov 2016 23:31:11 +0100
Message-ID: <CAF+90c9veg4hwrim3i_2CQ3n7ubLcK_J4qSEtpQd3H1DnEGa0Q@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: =?UTF-8?Q?Pedro_Magalh=C3=A3es?= <mail@pmmaga.net>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1146d9cee44ac90540a97600
Subject: Re: [PHP-DEV] Binary string forward compatibility removal
From: nikita.ppv@gmail.com (Nikita Popov)

--001a1146d9cee44ac90540a97600
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 6, 2016 at 8:56 PM, Fran=C3=A7ois Laupretre <francois@php.net> =
wrote:

> Hi,
>
> it was stated during the pre-7 discussions, that this flag would be kept
> for possible future unicode-compliant developments. So, people needing
> binary strings are still encouraged to use the flag, even if it is not us=
ed
> in the current versions.
>
> Regards
>
> Fran=C3=A7ois
>

I don't remember any specific on-list discussion on this topic, but my
general understanding is that at this point the unicode by default approach
has sailed. We may see something like u"" literals in the future (iirc this
was suggested during the UString discussion), but we quite certainly are
not going to change the default interpretation of strings -- it would cause
too much breakage.

Nikita

--001a1146d9cee44ac90540a97600--