From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NZmYW-0005Rw-Rg
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:38:12 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NZmYR-0005Kq-LL
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:38:12 -0500
Received: from [199.232.76.173] (port=43707 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NZmYR-0005Ke-Gs
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:38:07 -0500
Received: from mail-iw0-f188.google.com ([209.85.223.188]:50048)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NZmYR-0002Yf-22
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:38:07 -0500
Received: by iwn26 with SMTP id 26so4791164iwn.14
	for <qemu-devel@nongnu.org>; Tue, 26 Jan 2010 06:38:06 -0800 (PST)
Message-ID: <4B5EFE4B.7070109@codemonkey.ws>
Date: Tue, 26 Jan 2010 08:38:03 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH] win32: use PRId64 instead of %lld
References: <1264368221-3040-1-git-send-email-hpoussin@reactos.org>	<20100125100905.GA9019@redhat.com>	<20100125120348.461ce622@doriath>	<m3k4v6s14m.fsf@blackfin.pond.sub.org>	<20100125132719.23a483cf@doriath>	<20100125153838.GB11161@redhat.com>	<20100126094329.70719b6f@doriath>	<4B5EE450.9090004@linux.vnet.ibm.com>
	<4B5EF45B.30001@redhat.com>	<4B5EF6C1.2020105@linux.vnet.ibm.com>
	<4B5EF856.4050006@redhat.com>
In-Reply-To: <4B5EF856.4050006@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Herve Poussineau <hpoussin@reactos.org>, Markus Armbruster <armbru@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>

On 01/26/2010 08:12 AM, Avi Kivity wrote:
> On 01/26/2010 04:05 PM, Anthony Liguori wrote:
>> On 01/26/2010 07:55 AM, Avi Kivity wrote:
>>> The risk is that if we support a private extension (like '') and 
>>> then json is officially extended to support a conflicting or similar 
>>> syntax with a different meaning, then we cannot advance to the next 
>>> revision of json without breaking compatibility.
>>
>> The paragraph I quoted from the RFC seems to suggest that the authors 
>> of JSON boxed themselves in with respect to extending JSON.  The 
>> reason being that a conforming implementation is given free reign to 
>> extend with "non-JSON forms or extensions".  That would seem to 
>> prevent any extension.
>
> A json generator is required to generate conforming text.  So there 
> are three choices:
>
> - reject 's
> - unofficially accept 's, nonconforming generators break if json 
> changes, nor our problem
> - officially accept 's, look stupid when json changes
>
>>
>> Keep in mind, JSON is a proper subset of ECMAScript which means the 
>> likelihood of extension going outside of ECMAScript would be 
>> extremely unlikely.  I don't expect JSON is ever going to change.
>
> Who knows?  Let's not take unnecessary risks.

Keep in mind, I've already agreed to not allow '' strings for external 
JSON.  The only reason the thread's still alive is because we like to 
argue apparently :-)  Single quoted strings are not sufficiently useful 
to warrant taking any risks here.

Regards,

Anthony Liguori