From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NIieC-000847-EQ for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:01:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NIie7-0007zY-5t for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:01:31 -0500 Received: from [199.232.76.173] (port=41442 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NIie6-0007zF-QB for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:01:26 -0500 Received: from e6.ny.us.ibm.com ([32.97.182.146]:46674) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NIie6-0006N0-J5 for qemu-devel@nongnu.org; Thu, 10 Dec 2009 08:01:26 -0500 Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e6.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id nBACutqh012482 for ; Thu, 10 Dec 2009 07:56:55 -0500 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id nBAD1Px6105502 for ; Thu, 10 Dec 2009 08:01:25 -0500 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id nBAD1Pon002200 for ; Thu, 10 Dec 2009 11:01:25 -0200 Message-ID: <4B20F122.4070204@linux.vnet.ibm.com> Date: Thu, 10 Dec 2009 07:01:22 -0600 From: Anthony Liguori MIME-Version: 1.0 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Anthony Liguori , qemu-devel@nongnu.org, Luiz Capitulino 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. -- Regards, Anthony Liguori