Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43230
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.218.180 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type:content-transfer-encoding;
        b=KaX+0huhkNDoWd2tJfBQspvR0musoepy/vC9VWYOxrV0jx27qv78/M4PajgiDN8cXi
         Ig1JIIw1aRAtz213fYuH63QwbEQJDgafgbx9uABuJ+aGtDKn4bUBHsTbKh5CZs8cS+YH
         DIV1pb9QRo9oxx0UGreYpT4L+DjSQCjccGPj0=
MIME-Version: 1.0
Reply-To: RQuadling@googlemail.com
In-Reply-To: <49AC0CB7.6@macvicar.net>
References: <10845a340903020821v718bc762g243864f7e098ee1c@mail.gmail.com>
	 <49AC08EA.5000105@macvicar.net>
	 <10845a340903020836u67ba1600qd4be7101f4256863@mail.gmail.com>
	 <49AC0CB7.6@macvicar.net>
Date: Mon, 2 Mar 2009 20:02:52 +0000
Message-ID: <10845a340903021202o725a4899t453fde062e45c8c@mail.gmail.com>
To: Scott MacVicar <scott@macvicar.net>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Patch and test cases too for
From: rquadling@googlemail.com (Richard Quadling)

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
>

When it is in JSON, it isn't an object, but an object hash, similar,
as I understand things, to the differences between a class definition
and an instance. Or, I suppose more like an object serialization and
an object.

PHP_JSON_FORCE_OBJECT would be ideal.

Thank you.

-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"