Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42266
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error)
Message-ID: <494698D3.2030801@lerdorf.com>
Date: Mon, 15 Dec 2008 09:50:11 -0800
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: json_encode()
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Ok, so as promised I ran some of the options we have that came up last
week by Douglas Crockford.

1. Document the fact that if you want to strictly conform to the JSON
   spec and be sure your json_encode output will work in various JSON
   parsers, you have to pass it a PHP array or object.

2. Remove support for basic types entirely and throw an error if you
   pass json_encode() something that is not an array or an object.

3. Wrap basic types in an array [] by default and perhaps add an option
   to json_encode() to skip the wrapper.

He would prefer option 1.

-Rasmus