Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72926
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53176168.50305@lerdorf.com>
References: <CAMUwpuRkkaPHoFabtKA1ypfK6T_mDkGwtbMM3GRFaJPQBVDK3A@mail.gmail.com>
	<53176168.50305@lerdorf.com>
Date: Wed, 5 Mar 2014 19:06:43 +0100
Message-ID: <CAEZPtU5imvkn_Y=bhnW3S+mdeE+Bmku_YgaJ9u_32cQ4P1eKdQ@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Julien Pauli <jpauli@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHP6 thoughts about Engine changes
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Mar 5, 2014 at 6:39 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> On 3/5/14, 5:56 AM, Julien Pauli wrote:
>> Hey,
>>
>> I wrote a wiki page about my thoughts for engine BC breaking changes
>> in the next PHP5++ (PHP6 ?)
>>
>> As usual, those are actually just thoughts.
>> Anyone may (should ?) improve the wiki page (keeping a readable
>> structure) sharing his own knowledge and thoughts :-)
>>
>> Any debate for any (relevant) subject can start here.
>>
>> I think that PHP5.6 final release is a good starting point for first
>> milestones and first ideas throught code.
>>
>> https://wiki.php.net/ideas/php6/engine
>
>  Note also that Unicode is not
> even mentioned.

Unicode has its own page and section, that's why.

> The main failure of the previous PHP6 attempt wasn't actually the choice
> of UTF-16 as some people like to claim,

Right, but the main failure in Unicode support was UTF-16 (to clarify :).

However you are right. I have the feeling that this list is very
optimistic, but a couple of things should be considered (jit f.e. and
APIs cleanup for example).

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org