Thursday, January 06, 2005 7:43 PM
The year 2038 bug may prove very grave... Or not...
Not being a bitwise (hehe) programmer, I'm not too enlightened by the code samples, but nevertheless it's quite interesting to read about. In short, on January 10, 2004 some systems may display an incorrect date - and on "Tue Jan 19 03:14:07 2038", who knows what'll happen?