Re: [Qemu-devel] Use a hex string

[Anthony Liguori]

On 05/23/2011 06:02 PM, Jamie Lokier wrote:
> 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?

This doesn't change the fundamental issue here.  Javascript's internal 
representation for integers isn't 2s compliment, but IEEE794.  This 
means the expectations about how truncation/overflow is handled is 
fundamentally different.

Regards,

Anthony Liguori

> 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