Closed HexDecimal closed 2 months ago
For all I remember it's possible Julian encodes negative values in the input.
That wouldn't be ideal, but it's solvable. I could make a slightly renamed function to handle these if it's an issue.
I think the domain of each of these is pretty well known and falls in the positive range of the signed char. It should be safe even with whatever the heck Julian is doing IIUC.
Looking up the standard docs, 0x00 characters have the same results as 0x01. I can't find any way to explain or justify these macros, casting to
unsigned char
would've been more correct. Behavior is defined for ASCII characters, and for non-ASCII these are not the right tools anyways.Related to #12