Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47172
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain iki.fi from 204.13.248.72 cause and error)
Message-ID: <4B9A7E49.8020301@iki.fi>
Date: Fri, 12 Mar 2010 19:47:53 +0200
Reply-To: jani.taskinen@iki.fi
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc11 Thunderbird/3.0.3
MIME-Version: 1.0
To: Moriyoshi Koizumi <mozo@mozo.jp>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <4B9926E8.4080202@lerdorf.com> <cd1fb7541003120838r6a268b92ld6fa09c332f26735@mail.gmail.com>
In-Reply-To: <cd1fb7541003120838r6a268b92ld6fa09c332f26735@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6
From: jani.taskinen@iki.fi (Jani Taskinen)

Is that new implementation in trunk already? Is it (or will it be) 
backwards compatible with the current one?

--Jani


On 03/12/2010 06:38 PM, Moriyoshi Koizumi wrote:
> I'd love to see my brand-new mbstring implementation in the release.
> Dropping mbstring completely won't be any good because lots of
> applications rely on it, but I don't really want to maintain the funky
> library bundled with it.
>
> Moriyoshi
>
> On Fri, Mar 12, 2010 at 2:22 AM, Rasmus Lerdorf<rasmus@lerdorf.com>  wrote:
>> Ah, Jani went a little crazy today in his typical style to force a
>> decision.  The real decision is not whether to have a version 5.4 or
>> not, it is all about solving the Unicode problem.  The current effort
>> has obviously stalled.  We need to figure out how to get development
>> back on track in a way that people can get on board.  We knew the
>> Unicode effort was hugely ambitious the way we approached it.  There are
>> other ways.
>>
>> So I think Lukas and others are right, let's move the PHP 6 trunk to a
>> branch since we are still going to need a bunch of code from it and move
>> development to trunk and start exploring lighter and more approachable
>> ways to attack Unicode.  We have a few already.  Enhanced mbstring and
>> ext/intl.  Let's see some good ideas around that and work on those in
>> trunk.  Other features necessarily need to play along with these in the
>> same branch.  I refuse to go down the path of a 5.4 branch and a
>> separate Unicode branch again.
>>
>> The main focus here needs to be to get everyone working in the same branch.
>>
>> -Rasmus
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>