Friday, May 18, 2007

The new Y2K Problem: Y292,277,026,596

You may remember some distress around supposed Y2K issues several years ago. Many of those systems moved to storing four digits for years. Some other systems that used a slightly more technically clean approach still had a Y2038 problem. This has since been fixed for the most part in a number of ways. For instance:

Date/Time Functions in PHP 5.1 and up [use] a (signed) 64-bit value [introducing] a new wraparound date in about 290 billion years, on Sunday, December 4, 292,277,026,596. However, this problem is not widely regarded as a pressing issue.

No comments: