These "large" numbers, especially the result of the modulo operator, aren't actually messed up. It's simply how signed integers are represented in binary: the most significant bit (31 in these examples) is set if the number is negative, and the remaining bytes are the two's complement of the negative value, e.g. the less bits are set, the more "negative" the number gets. Static casting such a large unsigned value to its signed counterpart will give the proper result. Working on assembly level, it's way clearer to see, because the CPU itself doesn't concern itself with signed or unsigned types at all. It'll just do the binary math, and set flags (negative, carry and overflow) according to the result (based on bits set in the input and output values) of an add/subtract operation. The compiler then generates the code in accordance to the declarations in the C/C++ code and interprets it as such.
![ใจเสาะบนเกาะนาคี - อ๊ะอาย สกุณาพร เสียงวิหค [Official MV] | ค่ายเพลงเป็นหนึ่ง](http://i.ytimg.com/vi/jbcmGQkfyOg/mqdefault.jpg)
These "large" numbers, especially the result of the modulo operator, aren't actually messed up. It's simply how signed integers are represented in binary: the most significant bit (31 in these examples) is set if the number is negative, and the remaining bytes are the two's complement of the negative value, e.g. the less bits are set, the more "negative" the number gets. Static casting such a large unsigned value to its signed counterpart will give the proper result.
Working on assembly level, it's way clearer to see, because the CPU itself doesn't concern itself with signed or unsigned types at all. It'll just do the binary math, and set flags (negative, carry and overflow) according to the result (based on bits set in the input and output values) of an add/subtract operation. The compiler then generates the code in accordance to the declarations in the C/C++ code and interprets it as such.
Oh...
back to the memories when I was traumatized by C++ at Computer Science Class at College...
before stopping this disaster by Python...
😏
use odin instead. It fixes this.
Not a problem in Ada I think. Gamedev in Ada again? 😅