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
