Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37838
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 64.233.170.184 cause and error)
Message-ID: <483711EE.5060506@gravitonic.com>
Date: Fri, 23 May 2008 11:50:22 -0700
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807)
MIME-Version: 1.0
To: Steph Fox <steph@zend.com>
CC: internals <internals@lists.php.net>
References: <00a701c8bcfb$cdfa5f50$4401a8c0@foxbox>
In-Reply-To: <00a701c8bcfb$cdfa5f50$4401a8c0@foxbox>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] BC an' all that
From: andrei@gravitonic.com (Andrei Zmievski)

Because the majority of use cases involving strings do not involve 
binary strings. Or, as Rasmus said, "logic".

-Andrei

Steph Fox wrote:
> Hi all,
> 
> Tony's not alone, I'm also playing with PHP 6 today.
> 
> As Edward mentioned when I started talking about the upgrade path, we 
> don't have a way to cope with the (binary)|(b) cast prior to PHP 5.2.1. 
> It's arguable that most people will have access to PHP > 5.2.1, but 
> that's not 100% useful if you have something you'd like to 'just work' 
> regardless of other peoples' updates. Personally I'm stuck with the 
> choice of making the default phar stub forward compatible or backward 
> compatible - there's no way to do both.
> 
> Can someone please explain why (string) isn't a pseudonym for (binary) 
> in PHP 6.0? There's probably a very good reason and I'm just not seeing 
> it... but it would go a long way to solving the problem if it were.
> 
> - Steph
>