From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58242) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNUjr-0003kU-4B for qemu-devel@nongnu.org; Fri, 20 May 2011 14:47:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNUjq-0004bq-0G for qemu-devel@nongnu.org; Fri, 20 May 2011 14:47:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36370) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNUjp-0004bk-N5 for qemu-devel@nongnu.org; Fri, 20 May 2011 14:47:53 -0400 Date: Fri, 20 May 2011 19:47:50 +0100 From: "Richard W.M. Jones" Message-ID: <20110520184750.GX27503@amd.home.annexia.org> References: <20110520180331.GA21837@amd.home.annexia.org> <4DD6AEB9.6060506@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DD6AEB9.6060506@codemonkey.ws> Subject: Re: [Qemu-devel] [PATCH] qemu: json: Fix parsing of integers >= 0x8000000000000000 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Luiz Capitulino On Fri, May 20, 2011 at 01:11:05PM -0500, Anthony Liguori wrote: > JSON only supports int64_t. By the way, where does this information come from? The JSON RFC fails to define the range of numbers at all, just leaving it completely up to the application, and if JSON is based on Javascript then it would use double for numbers [a terrible idea from a qemu p.o.v -- I'm just pointing out that's what JS does]. So are you saying that JSON as defined in qemu defines numbers as int64_t, or is there something else I'm missing? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org