Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86101
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <55416547.9060602@gmail.com>
References: <CAJW__o2t+kWTaR2Gz5S=07TCaKQTA257pgrv008V509iR5ot0A@mail.gmail.com>
	<55416547.9060602@gmail.com>
Date: Thu, 30 Apr 2015 16:24:59 -0700
Message-ID: <CAESVnVp_gjc=Pih2yiX7M3Mfo7qJXz4MLbnHwnkKoNuSSgz0ew@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Kalle Sommer Nielsen <kalle@php.net>, Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Remove old PHP6 forward compatibility
From: pollita@php.net (Sara Golemon)

On Wed, Apr 29, 2015 at 4:12 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>> Back when PHP6 was actually a thing, we added the 'b' string literal
>> prefix and the (binary) cast to be forward compatible with PHP6,
>> however since the entire unicode strings part were dropped, these are
>> no longer needed.
>>
>> I think its safe to remove these 2, and take it as a lession learned,
>> to safely and selectively added forward compatibile features.
>
> Why remove it? I'm not sure what removing it would improve.
>
Agreed. PHP6 dying on the vine doesn't establish that we'll never have
baked-in unicode support.  Better to keep this around to improve
compatibility when/if we revisit this.

-Sara