Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43312
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.158 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=GrNklMCJyEuV2DnxttJM1BvJ6ugINN23b1uOfRlS0AO1I8a++JT3xCFF173ua3TKLL
         GiD9pjt07jCahxXqG9Oxq9Ho4knShGy8Upm5RhMU/qXzaYWpuQvti8PHw96KGtA1aK0T
         g4f9nCc5Ci9r4v/RLouVhfqKco0R4bIxyYsjQ=
MIME-Version: 1.0
In-Reply-To: <10845a340903100332v32aaa2bbs20316c2aea7738a5@mail.gmail.com>
References: <10845a340903020821v718bc762g243864f7e098ee1c@mail.gmail.com>
	 <49AC08EA.5000105@macvicar.net>
	 <10845a340903020836u67ba1600qd4be7101f4256863@mail.gmail.com>
	 <49AC0CB7.6@macvicar.net>
	 <10845a340903100332v32aaa2bbs20316c2aea7738a5@mail.gmail.com>
Date: Wed, 11 Mar 2009 20:25:13 +0100
Message-ID: <8f5c52fe0903111225lbbfd07ek7f51c9f1f31877c0@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001636c5a9b1c0b7580464dcd34f
Subject: Re: [PHP-DEV] Patch and test cases too for
From: christopher.oestlund@gmail.com (=?UTF-8?Q?Christopher_=C3=96stlund?=)

--001636c5a9b1c0b7580464dcd34f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I think this behavior is a bit odd too:

php -r "echo json_encode(array(0=>'test'));" // ["test"]
php -r "echo json_encode(array(1=>'test'));" // {"1":"test"}



On Tue, Mar 10, 2009 at 11:32 AM, Richard Quadling <rquadling@googlemail.com
> wrote:

> 2009/3/2 Scott MacVicar <scott@macvicar.net>:
> > Richard Quadling wrote:
> >> 2009/3/2 Scott MacVicar <scott@macvicar.net>:
> >>> Richard Quadling wrote:
> >>>> Hi.
> >>>>
> >>>> Regarding http://bugs.php.net/bug.php?id=47493, I've supplied a patch
> >>>> to the unit tests too.
> >>>>
> >>>> Any chance this could get committed to 5.2+
> >>>>
> >>> I'm too convinced of the parameter name and I don't think its something
> >>> that should be added to 5.2.9 since its a feature.
> >>>
> >>> Scott
> >>>
> >>
> >> 5.3+ would be OK then.
> >>
> >> As to the param name, I'm not actually changing the name, just adding
> >> another flag.
> >>
> >> In javascript's terminology,the output is an array ...
> >>
> >> []
> >>
> >> or a hash
> >>
> >> {}
> >>
> >> So forcing a hash for arrays is pretty much what would be wanted and I
> >> as I comment in the request, we have a "force" option when coming FROM
> >> json data ... json_decode ( string $json [, bool $assoc= false [, int
> >> $depth= 512 ]] )
> >>
> >> And the "name" of the param here is appropriate to PHP's use (assoc is
> >> not part of JSON's or JS's terminology).
> >>
> >> If you can think of a better name for the flag, then I'd be glad to use
> it.
> >>
> >
> > The JSON spec refers to them as arrays or objects though, as does our
> > documentation I believe.
> >
> > PHP_JSON_FORCE_OBJECT
> >
> > I however have another patch for more strict encoding so I'll try to
> > roll this in a single update.
> >
> > Scott
> >
>
> First of all, this isn't a "why is this not done yet" message. Honestly.
>
> Do you have any timeframe for this though?
>
> Do you think it will be ready for 5.3RC1?
>
> Thank you,
>
> Richard Quadling.
>
> --
> -----
> Richard Quadling
> Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
> "Standing on the shoulders of some very clever giants!"
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001636c5a9b1c0b7580464dcd34f--