The Y2k date issue was caused by the fact that computers were programmed to add a two digit number to some epoch (most notably 1900). So 100 became 00 and was added to 1900 to become 1900. This was corrected by increasing the number of digits used to store the year. The next date issue will occur in 2038 when the date field (a 32 bit signed integer) runs out of room to hold the number of milliseconds since the epoch. The fix for this will be a little more elaborate and will most likely involve the use of 64 bit integer.

Here is a perl script to see what time your computer will return when the Y2k38 hits. It will return the second just before and just after the event.

More »