Unsigned Types and Java about flatbuffers HOT 6 CLOSED

Good point, I will.

from flatbuffers.

Or may be you could use higher precision for unsigned types, for example for ubyte in buffer use short in java and for ushort in buffer use int in java.

from flatbuffers.

It really depends what the unsigned item represents how you want to deal
with it.

You can convert a byte to a short using: (short)(mybyte & 0xff)

Question is, should the generated API always do that for you, or should you
do that only when necessary. I gravitate to the latter.

On Sat, Jun 21, 2014 at 5:17 AM, bml13 [email protected] wrote:

Or may be you could use higher precision for unsigned types, for example
for ubyte in buffer use short in java and for ushort in buffer use int in
java.

—
Reply to this email directly or view it on GitHub
#9 (comment).

from flatbuffers.

I think it is the API who should do that always, since the user defined a field as unsigned (eg. ubyte) then he should get it as unsigned value, because if he wanted it signed then he should define as signed (eg. byte). I propose to to return both ushort and ubyte as int. Or it should be an option in the compiler.

from flatbuffers.

You're right, that makes more sense.

But uint as.. long? and ulong still as long?

from flatbuffers.

Yes you can return uint as long, and for ulong you can say in the documentation that it is not supported only long is supported.

from flatbuffers.