The origin of the comment is related to assuring that the code’s timestamp fields were not potentially subject to the Y2038 overflow problem (on 32 bit signed integers), as depicted in this thread. 32 bit unsigned integers manage to postpone the problem until next century ...
I figure that the core code has been verified on multiple occasions to be Y2038 free, though in general terms, we’d likely hear quite a bit about it as we close into the said year.
Topic: What does 'int' mint in Bitcoin (Read 137 times)
It's about a data type in the code or data.
The thing is that a signed int (32 bit signed integer) takes values between -2,147,483,648 and 2,147,483,647,
while unsigned int goes between 0 and 4,294,967,295
Clearly Satoshi meant that in case an error is found in his code, that has to be fixed before a big number is reached (bigger than 2,147,483,647), because in case of signed int that will mean an overflow to negative numbers.
The thing is that a signed int (32 bit signed integer) takes values between -2,147,483,648 and 2,147,483,647,
while unsigned int goes between 0 and 4,294,967,295
Clearly Satoshi meant that in case an error is found in his code, that has to be fixed before a big number is reached (bigger than 2,147,483,647), because in case of signed int that will mean an overflow to negative numbers.
"int" is short for integer which is a whole number (without fraction) that can be positive, negative, or zero. https://en.wikipedia.org/wiki/Integer
Pardon my ignorance. I just read this sentence and I don't get it.
"There should not be any signed int. If you've found a signed int somewhere, please tell me (within the next 25 years please) and I'll change it to unsigned int." -- Satoshi
"There should not be any signed int. If you've found a signed int somewhere, please tell me (within the next 25 years please) and I'll change it to unsigned int." -- Satoshi
Jump to: