Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96754
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 74.125.82.48 cause and error)
MIME-Version: 1.0
In-Reply-To: <7A.F8.33116.E57DF185@pb1.pair.com>
References: <cdd4edeaf066e73ca2ebdede5d5c535b@pmmaga.net> <7A.F8.33116.E57DF185@pb1.pair.com>
Date: Mon, 7 Nov 2016 07:18:57 +0000
Message-ID: <CAL=_i_n8NHTR-e5HGFQY1Dm-=+TripTacfOkvKF2r+jq7DriFQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1148da6e5c7fa60540b0d619
Subject: Re: [PHP-DEV] Re: Binary string forward compatibility removal
From: pthreads@pthreads.org (Joe Watkins)

--001a1148da6e5c7fa60540b0d619
Content-Type: text/plain; charset=UTF-8

Morning Andrea,

    Who is widely deploying something that does absolutely nothing ?

    The only reason to keep it would be that we are going to change the
default representation, as pointed out we're not.

    This cannot have been left in for considered reasons, it was just
forgotten about.

Cheers
Joe

On Mon, Nov 7, 2016 at 1:22 AM, Andrea Faulds <ajf@ajf.me> wrote:

> Hi Pedro,
>
> I don't support this removal.
>
> Currently, yes, the flag doesn't do anything, and it's unlikely to do so
> in future, as Nikita points out.
>
> However, it's not improbable that we might see a `u` flag in future, and
> if that was added, `b` might still be useful as an explicit counterpart.
>
> Anyway, this feels like deprecation for its own sake. As you point out,
> removing this breaks widely-deployed code. When the benefit of removal is
> negligible, and it breaks existing code, I don't think it can be justified.
>
> Thanks.
> --
> Andrea Faulds
> https://ajf.me/
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a1148da6e5c7fa60540b0d619--