Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21607
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43D1960D.2060902@lerdorf.com>
Date: Fri, 20 Jan 2006 18:01:49 -0800
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: Andi Gutmans <andi@zend.com>
CC: internals@lists.php.net, omar@rmilk.com, crock@yahoo-inc.com
References: <43D13AAE.1030409@lerdorf.com>	<7.0.0.16.2.20060120134701.04186f60@zend.com>	<43D1625C.3030001@lerdorf.com> <7.0.0.16.2.20060120170223.041fb8d0@zend.com>
In-Reply-To: <7.0.0.16.2.20060120170223.041fb8d0@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] JSON inclusion in core
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Andi Gutmans wrote:
> Yeah, but the main problem with this kind of stuff is when you start 
> mapping classes and even references. I think it requires some additional 
> pluming to be really useful for writing robust JavaScript<-->PHP 
> connectivity so that it's flexible enough for all those PHP packages to 
> start using it.
> I'm +1 for including JSON but not on the way the API is defined right now.

I guess I am confused.  Javascript, and thus JSON, has no concept of an 
object.  It has something it calls an object, but that is just an 
associative array.  Are you trying to layer some other syntax on top of 
JSON to convey more meaning than what JSON/Javascript natively supports?

I have looped in Douglas Crockford on this.  I am about to hop on a 
plane and will be somewhat out of touch for the next couple of days, but 
he is the authority on this stuff so please run your proposed api by him.

-Rasmus