From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:60327)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jamie@shareable.org>) id 1QOe8p-0002Gg-CF
	for qemu-devel@nongnu.org; Mon, 23 May 2011 19:02:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jamie@shareable.org>) id 1QOe8n-0008SE-CB
	for qemu-devel@nongnu.org; Mon, 23 May 2011 19:02:27 -0400
Received: from mail2.shareable.org ([80.68.89.115]:43100)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jamie@shareable.org>) id 1QOe8n-0008S3-4L
	for qemu-devel@nongnu.org; Mon, 23 May 2011 19:02:25 -0400
Date: Tue, 24 May 2011 00:02:22 +0100
From: Jamie Lokier <jamie@shareable.org>
Message-ID: <20110523230222.GL969@shareable.org>
References: <20110520180331.GA21837@amd.home.annexia.org>
	<4DD6AEB9.6060506@codemonkey.ws>
	<20110523130411.GR24143@redhat.com>
	<4DDA620F.1090308@codemonkey.ws>
	<20110523134021.GT24143@redhat.com> <4DDA663F.30907@codemonkey.ws>
	<m3fwo532xo.fsf@blackfin.pond.sub.org>
	<4DDA7829.5090103@codemonkey.ws>
	<20110523151948.GJ27503@amd.home.annexia.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110523151948.GJ27503@amd.home.annexia.org>
Subject: [Qemu-devel] Use a hex string (was: [PATCH] qemu: json: Fix parsing
	of integers >= 0x8000000000000000)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>

Richard W.M. Jones wrote:
> The problem is to be able to send 64 bit memory and disk offsets
> faithfully.  This doesn't just fail to solve the problem, it's
> actually going to make it a whole lot worse.

Such offsets would be so much more readable in hexadecimal.

So why not use a string "0xffff800012340000" instead?

That is universally Javascript compatible as well as much more
convenient for humans.

Or at least, *accept* a hex string wherever a number is required by
QMP (just because hex is convenient anyway, no compatibility issue),
and *emit* a hex string where the number may be out of Javascript's
unambiguous range, or where a hex string would make more sense anyway.

-- Jamie