From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N3vaF-0004OF-Lk
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:48:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N3va9-0004Ib-N9
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:48:18 -0400
Received: from [199.232.76.173] (port=46790 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N3va9-0004ID-FC
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:48:13 -0400
Received: from mail-ew0-f221.google.com ([209.85.219.221]:60522)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1N3va8-00024D-Nt
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:48:12 -0400
Received: by ewy21 with SMTP id 21so3121690ewy.8
	for <qemu-devel@nongnu.org>; Fri, 30 Oct 2009 10:48:11 -0700 (PDT)
Message-ID: <4AEB26D6.5040308@codemonkey.ws>
Date: Fri, 30 Oct 2009 12:48:06 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [RFC 0/7] QError v1
References: <1256841750-15228-1-git-send-email-lcapitulino@redhat.com>	<4AEA133A.8010906@redhat.com>
	<20091030102809.1c520282@doriath>	<4AEAE261.5030908@redhat.com>
	<4AEAE56E.8040309@us.ibm.com>	<20091030162849.GH3579@shareable.org>	<20091030171514.GI21617@redhat.com>
	<4AEB235B.5000104@redhat.com>
In-Reply-To: <4AEB235B.5000104@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: Paolo Bonzini <pbonzini@redhat.com>
Cc: hollisb@linux.vnet.ibm.com, Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>

Paolo Bonzini wrote:
> On 10/30/2009 06:15 PM, Daniel P. Berrange wrote:
>> If we're going to use JSON we should be 100% compliant with the JSON
>> spec, not extend it. By adding custom QEMU extensions, we loose the
>> ability for programming language to trivially talk to QEMU using a
>> standard JSON parser, and instead everyone has to write custom client
>> side code yet again.
>
> The single-quoted-string extension is just to be used internally to 
> ease writing JSON templates in C.  All emitted text will go through 
> the JSON encoder, which will be conservative (no extensions) for the 
> reasons you mention.

Correct.  Furthermore, even our internal extensions should be as minimal 
as possible.  The only reason for allowing single quoted strings is that 
"{"\"key\": 32}" gets out of hand quickly.  It's not so bad in other 
languages that support single quoted strings but for C, it's really a 
necessary extension.

Regards,

Anthony Liguori