Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42248
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.227 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=RBtvtQJBTj640ojnyfn+m9MVUriRTiZ2R8tmM0dSlRadtakEgta7wwT4mdcT9pLZfq
         eKrPkbzVZM6EaVkfRNn1FyF07WirHOtZCfDnp2ZQ8pLnum9GbaPA918tZnYeiAoYqIU+
         2CrrZESVLQdzr3KrhrbPdwc4ixlrgYjpc+1+w=
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> <234C8048-A00D-4AEE-A23E-5FA10EA85D6D@gmail.com> <4944AD36.7070406@lerdorf.com>
Message-ID: <6C9F85B0-29B8-419C-8DD1-BA90135214D3@gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
In-Reply-To: <4944AD36.7070406@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: Sun, 14 Dec 2008 00:18:04 -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)

Do you mean a json_parse in javascript (like a better eval() I  
assume)? Thats what we were doing. Json is not supposed to be pure  
javascript either, but a serialized representation of variables like  
php's serialize(). So I would not expect a json string to be usable  
without using eval or something else in javascript first. We had to  
modify the php json_encode output to be wrapped with a couple extra  
braces for it to be able to be consumed properly on javascript (or  
maybe it was the other way around) - I just want to make sure we won't  
have to make special things like that in the future.

On Dec 13, 2008, at 10:52 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> Yes, but that would be going to a json_parse thing somewhere, not pure
> Javascript.
>
> -Rasmus
>
> mike wrote:
>> 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
>