From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N3vLu-0001WP-Ud
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:33:31 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N3vLo-0001Mg-10
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:33:28 -0400
Received: from [199.232.76.173] (port=53634 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N3vLn-0001MB-Q8
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:33:23 -0400
Received: from mx1.redhat.com ([209.132.183.28]:52174)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pbonzini@redhat.com>) id 1N3vLn-0008Jn-6I
	for qemu-devel@nongnu.org; Fri, 30 Oct 2009 13:33:23 -0400
Message-ID: <4AEB235B.5000104@redhat.com>
Date: Fri, 30 Oct 2009 18:33:15 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
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>
In-Reply-To: <20091030171514.GI21617@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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, hollisb@linux.vnet.ibm.com

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.

Paolo