Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29490
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error)
In-Reply-To: <fe05d1540705161256k4f2718d0m8e99e6c2d275c9cf@mail.gmail.com>
References: <1082866338.20070516162127@marcus-boerger.de> <fe05d1540705161256k4f2718d0m8e99e6c2d275c9cf@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <852842D7-B7AB-4BD5-A342-0D5DB0E7ABBC@gravitonic.com>
Cc: "Marcus Boerger" <helly@php.net>, internals@lists.php.net,
        "Andi Gutmans" <andi@zend.com>, "Dmitry Stogov" <dmitry@zend.com>
Content-Transfer-Encoding: 7bit
Date: Thu, 17 May 2007 11:51:29 -0500
To: Pierre <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] PHP 6 Preview
From: andrei@gravitonic.com (Andrei Zmievski)

On May 16, 2007, at 2:56 PM, Pierre wrote:
> 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.

Except you don't seem to reply to any of my emails or IRC chat requests.

> 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.

That refers only to the function coverage, not the core functionality.

> 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.

Correct.  Dmitry or I, or possibly Sara, have to finish that.

> 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.

I would request that you do not try to work on the input decoding  
feature since you proved very unreliable in the past.

Best regards,

-Andrei