Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29484
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.181 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=OxOeYyklRmCXo1UxanrX4E/FSxjp3eIjKK6VV0xK1j+Nb8B6VLPqQuXs3Ch1Xh8Qbc2G77IPUP6q5YfCb/P/kTsqk1fHch5b0vditnKpvMwUSCB+dlM6KEhyU3uVU3LyzMDFbVr39nA0bFOV3HuWsfb2BsqI5niYNHhBM0QBmB4=
Message-ID: <fe05d1540705161256k4f2718d0m8e99e6c2d275c9cf@mail.gmail.com>
Date: Wed, 16 May 2007 21:56:25 +0200
To: "Marcus Boerger" <helly@php.net>
Cc: internals@lists.php.net, "Andi Gutmans" <andi@zend.com>, 
	"Dmitry Stogov" <dmitry@zend.com>, 
	"Andrei Zmievski" <andrei@gravitonic.com>
In-Reply-To: <1082866338.20070516162127@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1082866338.20070516162127@marcus-boerger.de>
Subject: Re: [PHP-DEV] PHP 6 Preview
From: pierre.php@gmail.com (Pierre)

On 5/16/07, Marcus Boerger <helly@php.net> wrote:
> Hello internals,
>
>   I don't see any progress for PHP 6 in the last several months. And we
> head more and more into a situation where people no longer develop in
> HEAD and instead develop in 5.2 without caring to MFB.

Please tell these "people" to MFB. Everyone has to MFB or ask for help
if they don't have the time, knowledge or motivation.

> All I know is that we are waiting for the filter extension. As it appears
> right now, I do not see Pierre doing the job he offered so we need to find
> somebody else here. Anyone care to jump in who has the indepth knowledge?

This information is incorrect and misguided, please understand what
you are talking about before making inappropriate claims. Simply
asking me or really any other developer of the filter extension would
have been more productive. I do check my email, and am many times on
IRC.

The filter extension is not holding up PHP 6 except it does not yet
support unicode but that's not the point. Right now all of PHP is
60.56% unicode converted.

> And besides this filter issue, what are the remaining pieces to be done?

Now moving on, what you might be referring to is the upcoming input
encoding system (again, nothing to do with ext/filter). We have had
some (very) long discussions about what has to be done, including some
off list, and how to do it. As I remember, there are two people who
are in position to complete this task, both Dmitry and myself but
neither of us have had the time to finish it yet. The JIT at runtime
is done but the input decoding (callback, default values change,
errors, etc.) is not finished.

About the php6 todos in general, I have to take a look again to the
wiki and my todos for the extension I maintain. This long weekend may
be a good opportunity to do some planing.


--Pierre