Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47231
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.134 as permitted sender)
To: Derick Rethans <derick@php.net>
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>, PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <alpine.DEB.2.00.1003131123540.4153@kossu.derickrethans.nl>
References: <4B9926E8.4080202@lerdorf.com>
	 <alpine.DEB.2.00.1003131123540.4153@kossu.derickrethans.nl>
Content-Type: text/plain; charset="UTF-8"
Organization: php.net
Date: Sat, 13 Mar 2010 18:33:46 +0100
Message-ID: <1268501626.14276.51.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

On Sat, 2010-03-13 at 11:57 -0500, Derick Rethans wrote:
> So I would suggest the following things to do:
> 
> - get rid of Jani's play branch
> - move trunk to branches/FIRST_UNICODE_IDEA
> - put 5.2 in security fix only mode
> - pht 5.3 in bug fix only mode
> - start adding new features (traits, Ilia's scalar typehint patch, 
>   output buffering things) to the new trunk cloned from 5.3.
> - in the meanwhile, start working on patching in back Unicode support, 
>   but in small steps. Exactly which things, and how we'd have to find 
>   out. But I do think it needs to be a *core* language feature, and not 
>   simply solved by extensions. We also need to make sure everybody 
>   understands that Unicode isn't just about encodings, or charsets and 
>   that thre are differences between that. Education is going to be 
>   important (and adding Unicode back in small bits would certainly help 
>   there).

+1

johannes