Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33769 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73441 invoked by uid 1010); 5 Dec 2007 20:16:45 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 73420 invoked from network); 5 Dec 2007 20:16:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Dec 2007 20:16:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=markus@fischer.name; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=markus@fischer.name; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fischer.name from 213.46.255.22 cause and error) X-PHP-List-Original-Sender: markus@fischer.name X-Host-Fingerprint: 213.46.255.22 viefep18-int.chello.at Solaris 10 (beta) Received: from [213.46.255.22] ([213.46.255.22:64919] helo=viefep11-int.chello.at) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/45-20707-32707574 for ; Wed, 05 Dec 2007 15:16:41 -0500 Received: from genuine.home ([213.47.124.167]) by viefep11-int.chello.at (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20071205201613.QYLL29111.viefep11-int.chello.at@genuine.home>; Wed, 5 Dec 2007 21:16:13 +0100 Received: from chello213047124167.36.11.vie.surfer.at ([213.47.124.167] helo=[192.168.1.51]) by genuine.home with esmtpa (Exim 4.50) id 1J00f1-0005cJ-PE; Wed, 05 Dec 2007 21:16:03 +0100 Message-ID: <4757070C.2040505@fischer.name> Date: Wed, 05 Dec 2007 21:16:12 +0100 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Rasmus Lerdorf CC: Keryx Web , PHP Developers Mailing List References: <474F0EE7.8020201@php.net> <474F5F75.3030808@zend.com> <475081DD.90404@php.net> <4750B3CA.20405@zend.com> <475101FF.5080103@lerdorf.com> <475482AF.3050800@zend.com> <47548638.9020709@lerdorf.com> <475487D0.7050207@zend.com> <47549512.1000505@akbkhome.com> <4754DEA0.10105@php.net> <47569091.3020704@keryx.se> <475692A5.7020600@lerdorf.com> In-Reply-To: <475692A5.7020600@lerdorf.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=C2272BD0; url=http://markus.fischer.name/my_public_key.txt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: -29 X-Spam-Level: --- X-Spam-Report: Spam detection software, running on the system "genuine.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Rasmus Lerdorf wrote: > We should probably have done it this way right from > the beginning, but since we didn't and since we don't really want to > deal with the potential BC issues of changing working code, we have to > add it as an option at this point. [...] Content analysis details: (-3.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -3.3 ALL_TRUSTED Did not pass through any untrusted hosts -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0001] 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [213.47.124.167 listed in dnsbl.sorbs.net] 0.9 AWL AWL: From: address is in the auto white-list Subject: Re: [PHP-DEV] Proposed feature for json_encode() From: markus@fischer.name (Markus Fischer) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Rasmus Lerdorf wrote: > We should probably have done it this way right from > the beginning, but since we didn't and since we don't really want to > deal with the potential BC issues of changing working code, we have to > add it as an option at this point. As long as the output follows the JSON specs, would there really be any BC issues anyway? The \u syntax is part and has been part of the specs since the beginning. Are these real world concerns? thanks, - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHVwcM1nS0RcInK9ARApKRAJ0YIPBZYDzF9dGfo2f01kbaDuxtOACg1CYN TPV8cbTac48uz/xEe1seEtI= =FOW7 -----END PGP SIGNATURE-----