[kc]

Quote:

Originally Posted by Westie Some computers (or programs, look at C++ and unsigned integers (I believe, correct me if I'm wrong)) cannot handle negative values, so sometimes they can crash.

which is why Y2K happened (basically)

Alot of programs used just 2 digits for the year, and add 1900 to that, or even just add 19 infront of it, causing the year to appear to be 1900 on those programs, causing some to crash.

The next one of these errors happens in 2038. Which will cause all systems that use 32 bit integers to store the date. Which will turn negative on exactly "03:14:07 UTC on Tuesday, 19 January 2038"


Then another one is year 65,536.

I'm sure you have all seen the ping "65535", or that number as a players ammo when they don't have any guns? Well 65,535 is the largest number that can be represented by a 16 bit binary number. So the year 65536 is going to cause another negative problem with 16 bit systems.

There is actually loads of these, listed on wikipedia at http://en.wikipedia.org/wiki/Time_fo...d_storage_bugs

The best one, is the year 170,141,183,460,469,231,731,687,303,715,884,105,72 7. this is the year that 128-bit Unix time would reset to zero.