From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NIiyv-0008T2-LI
	for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:22:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NIiyp-0008N0-OI
	for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:22:56 -0500
Received: from [199.232.76.173] (port=48838 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NIiyp-0008Md-Hj
	for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:22:51 -0500
Received: from mx1.redhat.com ([209.132.183.28]:61284)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <armbru@redhat.com>) id 1NIiyp-0008Sk-0V
	for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:22:51 -0500
From: Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 06/19] monitor: do_info_cpus(): Use QBool
References: <1260376078-8694-1-git-send-email-lcapitulino@redhat.com>
	<1260376078-8694-7-git-send-email-lcapitulino@redhat.com>
	<m3ws0vumzi.fsf@crossbow.pond.sub.org>
	<4B20F122.4070204@linux.vnet.ibm.com>
Date: Thu, 10 Dec 2009 14:22:45 +0100
In-Reply-To: <4B20F122.4070204@linux.vnet.ibm.com> (Anthony Liguori's message
	of "Thu, 10 Dec 2009 07:01:22 -0600")
Message-ID: <m3ocm7neu2.fsf@crossbow.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>

Anthony Liguori <aliguori@linux.vnet.ibm.com> writes:

> Markus Armbruster wrote:
>> Do we want to specify the base for numbers in the JSON?
>>
>> If yes, why not use decimal everywhere?
>>
>> Aside, if we use hexadecimal in JSON at all, then I'd prefer addresses
>> to be hexadecimal.
>>   
>
> Hexadecimal is not valid to represent numbers in JSON.

In that case, there's no need to document the format of numbers for
every command.