Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37836
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.185 as permitted sender)
Message-ID: <00a701c8bcfb$cdfa5f50$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "internals" <internals@lists.php.net>
Date: Fri, 23 May 2008 18:38:24 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: BC an' all that
From: steph@zend.com ("Steph Fox")

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