Re: IOBuffer features

Per Hedbor wrote:

It would also break hstring reading rather badly, so you would still need the functions to read unsigned numbers internally.

Also, with native integers, as it turns out, it's fairly equal on x86_64 at least, where the integer operations are inlined.

Just add another function to read signed integers.

Shall we rename the read_int* to read_uint* then?

And as for byteorder, just add a switch to switch byteorder if the number of functions needs to be kept down for some reason.

Well, since IOBuffer is for efficiency and not for beauty, I guess it does not matter a lot if there are few or a lot of functions. Whatever is most efficient counts here, I'd say.