Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21611 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38924 invoked by uid 1010); 21 Jan 2006 02:32:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38908 invoked from network); 21 Jan 2006 02:32:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2006 02:32:10 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:12828] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id AD/44-10117-92D91D34 for ; Fri, 20 Jan 2006 21:32:10 -0500 Received: (qmail 15997 invoked from network); 21 Jan 2006 02:32:06 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 21 Jan 2006 02:32:06 -0000 Message-ID: <7.0.0.16.2.20060120183001.0421da58@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Fri, 20 Jan 2006 18:32:03 -0800 To: Rasmus Lerdorf Cc: Jani Taskinen ,internals@lists.php.net In-Reply-To: <43D19937.6050201@lerdorf.com> References: <43D13AAE.1030409@lerdorf.com> <7.0.0.16.2.20060120134701.04186f60@zend.com> <7.0.0.16.2.20060120160835.040c9f20@zend.com> <7.0.0.16.2.20060120165840.041fbf10@zend.com> <43D19937.6050201@lerdorf.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] JSON inclusion in core From: andi@zend.com (Andi Gutmans) At 06:15 PM 1/20/2006, Rasmus Lerdorf wrote: >I am all for the filter extension as well obviously, but I agree >there is a bit of cleanup needed and I have a bunch of things I'd >like to see in it, but none of them necessarily block adding it. Not sure about the functionality, and I agree some of it can probably way, but I would want to finalize the naming before so that we don't have to change it and have another BC mode. >As far as promising it for 5.1.0? I don't recall that being the >case. It wasn't ready when we rolled the first 5.1.0 packages. Yeah I don't remember that either but again, I'm all in favor, but let's just iron out the naming and other feedback which is deemed as critical (if it's just additional non-API affecting features, those can always be added later on) Andi >-Rasmus > >Andi Gutmans wrote: >>I've always been in favor of having ext/filter in standard PHP. >>It's time we added some security supporting features. >>Only thing I'd like to do before that is improve the naming >>conventions a bit. Functions filter_* and I think the constant >>naming like FL_* and FS_* is a bit confusing. But those are things >>that can be finalized and changed within a day. >>Andi >>At 04:51 PM 1/20/2006, Jani Taskinen wrote: >> >>> I'm not against this extension. I'd just very much like to >>> see the filter extension finally in core as was promised >>> for 5.1.0 once upon the time..IIRC. >>> >>> --Jani >>> >>> >>>On Fri, 20 Jan 2006, Andi Gutmans wrote: >>> >>>> >>>>JSON is actually useful for real-world apps and not only for >>>>buzzword-compliance :) >>>> >>>>At 02:02 PM 1/20/2006, Jani Taskinen wrote: >>>>> >>>>>yet-another-must-have-because-it-is-sexy-and-buzzword-compliant >>>>>extension..