Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25891 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47915 invoked by uid 1010); 29 Sep 2006 12:36:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 47900 invoked from network); 29 Sep 2006 12:36:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Sep 2006 12:36:36 -0000 X-Host-Fingerprint: 217.79.190.163 r163.red.fastwebserver.de Received: from [217.79.190.163] ([217.79.190.163:24776] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 15/06-06827-2531D154 for ; Fri, 29 Sep 2006 08:36:35 -0400 To: internals@lists.php.net,cschneid@cschneid.com (Christian Schneider) Date: Fri, 29 Sep 2006 14:36:25 +0200 Message-ID: <20060929143625.2b9ec272@pierre-u64> In-Reply-To: <451D0E3E.6000301@cschneid.com> References: <9D21C7F4-5269-47C2-B574-F563B378A4CF@prohost.org> <451CF1B4.4040503@cschneid.com> <451D0E3E.6000301@cschneid.com> Reply-To: pierre.php@gmail.com X-Newsreader: Sylpheed-Claws 2.5.0 (GTK+ 2.8.20; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Posted-By: 217.79.190.163 Subject: Re: [PHP-DEV] Filter Vote From: pierre.php@gmail.com (Pierre) On Fri, 29 Sep 2006 14:14:54 +0200 cschneid@cschneid.com (Christian Schneider) wrote: > While I agree with you the problem is that it's as of now unclear > who's in the driver seat of the filter extension: You or Derick. Forgot to answer to this specific part. Let me say it again: The leads of this extension are all active PHP Internals developers. The reason is simple, this extension affects PHP on each single request, it will be installed and available everywhere. Its code will be executed, whether you use filter or not. If I did not harass the list with my calls for reviews, feedbacks, tests or API proposals, we will still have a non working extension. An extension you can compile barely only on Derick's box and having segfaults than valid values. I'm not saying that the extension was badly implemented or designed, only that it was not ready to be bundled, even not ready to be tagged as beta. I brought it to the required stability (both from API and implementation) to be included in php, with the requested features or options. All my choices have been based on users request and public discussions and polls. The rest is pure politics and marketing crap. I refused to play this game to get things done in time because I am (and was) ready in time. Ok, I said all I have to say about this topic now :) -- Pierre