Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42234
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: Scott MacVicar <scott@macvicar.net>,
 PHP Developers Mailing List <internals@lists.php.net>
Message-ID: <996B6F15-A0BC-4DE9-9486-BD7716F543C1@pooteeweet.org>
To: Ilia Alshanetsky <ilia@prohost.org>
In-Reply-To: <FB99B6B8-A41C-4076-9CA1-646814E422B9@prohost.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 13 Dec 2008 19:05:18 +0100
References: <2D85B33E-889B-4214-9BB8-A12EFFFC641E@macvicar.net> <FB99B6B8-A41C-4076-9CA1-646814E422B9@prohost.org>
Subject: Re: [PHP-DEV] Re: Removing basic types from our JSON parser
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 13.12.2008, at 18:59, Ilia Alshanetsky wrote:

>
> On 12-Dec-08, at 10:50 PM, Scott MacVicar wrote:
>
>> Hi All,
>>
>> Basic types were added to our JSON decoder to PHP 5.2.1, this  
>> allows one to use json_encode / json_decode on any of our scalar  
>> types. Omar correctly identified #38680 as not a bug but it appears  
>> that Ilia added support for this anyway violating the RFC [1].  
>> Maybe there was a reason for this but I'm not sure why?
>
> PHP is typeless language, IMO its conductive to this design to allow  
> encoding of basic types via json_encode, it reduces the code when  
> communicating to/form JavaScript to avoid type detection. While it  
> does violate the RFC IMO the convenience of the feature is  
> definitely worth it.


well seems to me like its safer to stick with RFC as the default. if  
at all this should be optional. JSON is a standard and this requires  
everybody to follow it. so using something else should be a conscious  
decision that is also visible during code review.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org