Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19485
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4346E00A.8020504@prohost.org>
Date: Fri, 07 Oct 2005 16:52:26 -0400
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Andrei Zmievski <andrei@gravitonic.com>
CC: Derick Rethans <derick@php.net>, 
	PHP Developers Mailing List <internals@lists.php.net>
References: <Pine.LNX.4.62.0510061954140.13434@localhost> <99dd4f75f4ceebfe1c980cf439e97416@gravitonic.com>
In-Reply-To: <99dd4f75f4ceebfe1c980cf439e97416@gravitonic.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Unicode Implementation
From: ilia@prohost.org (Ilia Alshanetsky)

Andrei Zmievski wrote:
>> - we have a bit less BC.
> 
> 
> "A bit less"? I'd say it would break BC in a major way. People who want
> to upgrade to PHP 6 would need to rewrite a lot of their scripts.

I think most large applications will be in this boat anyway, we may as
well do it properly once, so we don't end up hacks on top of hacks just
for the sake of BC.

> We can try switching to _UNSAFE versions of the iterator macros - they
> assume well-formed UTF-16, so they will be somewhat faster.

We definitely need to look at that since if upgrading to 6.0 means a 3x
slower operation very few people will even consider upgrading.

Ilia