Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21612
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=WfBo0yHDUIR5VM0ZInMQ1RZ34OT4UHyFFc0DobkWLWUGgA+biHtr5opJPutOzG8vDfAvSW8BotxWLrF47sHd37r9bi0Rvil8523Dfezd/p6aN8UjzQ2sMVCnmLQ9jyv+O49bqSOKxVwdzvBxhEi03+rSNhqkZxnDnf4s9XQSbiE=
Message-ID: <7f3ed2c30601201853r39d4953dve719bc1c81c39520@mail.gmail.com>
Date: Sat, 21 Jan 2006 03:53:27 +0100
Sender: hannes.magnusson@gmail.com
To: Andi Gutmans <andi@zend.com>
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>, Jani Taskinen <sniper@iki.fi>, 
	internals@lists.php.net
In-Reply-To: <7.0.0.16.2.20060120183001.0421da58@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43D13AAE.1030409@lerdorf.com>
	<7.0.0.16.2.20060120134701.04186f60@zend.com>
	<Pine.LNX.4.61.0601210001030.14008@arfg.argcubovn.sv>
	<7.0.0.16.2.20060120160835.040c9f20@zend.com>
	<Pine.LNX.4.61.0601210250150.14237@arfg.argcubovn.sv>
	<7.0.0.16.2.20060120165840.041fbf10@zend.com>
	<43D19937.6050201@lerdorf.com>
	<7.0.0.16.2.20060120183001.0421da58@zend.com>
Subject: Re: [PHP-DEV] JSON inclusion in core
From: bjori@php.net (Hannes Magnusson)

On 1/21/06, Andi Gutmans <andi@zend.com> wrote:
> 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

http://benramsey.com/archives/pecl-input-filter/
quote: "Yet, recently (15 Nov), I noticed that Jani Taskinen (a.k.a.
"sniper") checked in some revisions with the comment "Prepare for
including in PHP core." This got me thinking, so I asked Derick, and
Derick confirmed that the Input Filter extension will be a part of the
PHP core in versions 5.1.1 and 6.0."

Never noticed any discussions about it in here about including it in PHP5.1=
.
I however would love to see it in the next release.

- Hannes

> 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..
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>