writing any kind of C code with large values or bitfields using types like "unsigned int" or "signed short int" instead of "uint32_t" or "int16_t" is risky...

Reply to this note

Please Login to reply.

Discussion

like, most C compilers will do what you expect, so it's fine, but it's not particularly portable since the C standard doesn't actually offer all that many guarantees for much of anything.

Excellent background information here!