Airbag currently puts 128-bit integers into native endianness. This
requires consumers of the code to know what the native byte order is, if
they want to parse the value into {high, low}. I think it would be better
if Airbag just provided the high/low pair.
Original issue reported on code.google.com by bry...@gmail.com on 2 Feb 2007 at 11:39
Original issue reported on code.google.com by
bry...@gmail.com
on 2 Feb 2007 at 11:39Attachments: