Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96755 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35077 invoked from network); 7 Nov 2016 11:26:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Nov 2016 11:26:26 -0000 X-Host-Fingerprint: 82.132.245.86 82-132-245-86.dab.02.net Received: from [82.132.245.86] ([82.132.245.86:28266] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/5B-33116-CD460285 for ; Mon, 07 Nov 2016 06:26:24 -0500 Message-ID: <2B.5B.33116.CD460285@pb1.pair.com> To: internals@lists.php.net References: <7A.F8.33116.E57DF185@pb1.pair.com> Date: Mon, 7 Nov 2016 11:26:11 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 82.132.245.86 Subject: Re: [PHP-DEV] Re: Binary string forward compatibility removal From: ajf@ajf.me (Andrea Faulds) Hi, Joe Watkins wrote: > Morning Andrea, > > Who is widely deploying something that does absolutely nothing ? PHAR uses (binary), or so Pedro's email says. > > The only reason to keep it would be that we are going to change the > default representation, as pointed out we're not. If we were adding it tomorrow, maybe, but `b` and the (binary) cast are already here. A high standard must be met for removing features. These aren't a security problem, nor a maintenance burden. There's not a good case for removing them and breaking backwards-compatibility > > This cannot have been left in for considered reasons, it was just > forgotten about. If it was to be removed, the time to do so would have been right after PHP 6's failure. But it's been years now. I'm unconvinced there's a strong case to remove it. Thanks for your reply. -- Andrea Faulds https://ajf.me/