an unsigned byte is not even thought of. Is this a rebellious choice of the authors?
It is a victim at the intersection of Rue de Computer Science and Reality Way, and a carry-over from Java, similar to 0x for hex literals rather than &H.
I am thankful that B4X Bytes at least accept values of 128..255, even if they won't give 'em back.
While we're here: the easiest way I know of to convert them from signed back to unsigned is
Bit.And(SignedByte, 0xFF)
(rather than the
If convolutions that are sometimes bandied about)
It's certainly painful knowing that I've started a serious project only to hit a road block this ridiculous.
More of a pot hole than a road block
but I share your pain
it irritates me daily too, and I would be be quite happy if there was a UByte type, or an option to default Bytes to unsigned. Although that then raises the question of: what also about Shorts, and even Ints and Longs?
edit: actually, I like UByte better, because that way doesn't break existing code like invoking an unsigned default option would