Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42246
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.234 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=references:message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:x-mailer:mime-version:subject:date:cc;
        b=tPaKHE4gzfnmEemgAe8teX0k6/qnUBFMtVLdsHYvd19k8BAxq9MzN9haDVDvDn/wbb
         vYbTpOe0jXNzI3b69BwmZtsT99QEvZk6AOde5RaRJx0T89NtxYRXpGUKEBF7mZBwkZs/
         x1XDk0iTlR6+KtEgPw8KqunBDtt0m57oxuU2c=
References: <2D85B33E-889B-4214-9BB8-A12EFFFC641E@macvicar.net> <1229150500.30719.201.camel@localhost> <4BA26FE8A9634178B4CEBEFA818810D2@VEGA> <15E310EAB433466EAF996B252CBED2BB@pc> <49448D66.2030501@lerdorf.com> <28139bc0812132210p1ed94f4ds40e31ff499cf2e7@mail.gmail.com> <7463F1E1-A880-479F-9584-30FFCED6E614@gmail.com> <4944AA37.9030400@lerdorf.com>
Message-ID: <234C8048-A00D-4AEE-A23E-5FA10EA85D6D@gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
In-Reply-To: <4944AA37.9030400@lerdorf.com>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 5G77)
Date: Sat, 13 Dec 2008 22:49:03 -0800
Cc: "moo.tinys" <moo.tinys@gmail.com>,
 Stan Vassilev | FM <sv_forums@fmethod.com>,
 PHP Developers Mailing List <internals@lists.php.net>
Subject: Re: [PHP-DEV] Removing basic types from our JSON parser
From: mike503@gmail.com (mike)

I can't give specifics (I'm mobile and I don't remember where the code  
would be anyway) but we had an issue with php and javascript exchange  
via json where the php output using json_encode and we had to wrap it  
with additional braces for it to be usable. Sorry for being vague,  
this thread reminded me of that which is why I wanted to voice off.

Thanks for the clarification (and thank you so much for PHP :))

On Dec 13, 2008, at 10:39 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> mike wrote:
>> Sorry for top posting. I see no reason why php should not interop  
>> with
>> javascript 100% as it should. I do not see a reason to create new
>> functions, parameters, etc. The existing should be expected to both
>> encode and decode json with javascript properly. If there is a  
>> mismatch
>> right now, then it should be fixed.
>
> There is no mismatch with Javascript now at all.  We spit out  
> perfectly
> valid Javascript.  There is only a slight mismatch with the JSON RFC
> which defines a stricter subset of Javascript than we are using.
>
> -Rasmus