Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re: 2038 bugby Abigail-II (Bishop) |
on Apr 11, 2003 at 07:26 UTC ( [id://249828]=note: print w/replies, xml ) | Need Help?? |
You'd make a mistake if you think the 2038 problem will
magically resolve itself if time_t is suddenly a 64 bit
integer. If it were that simple, wouldn't you think many
operating systems already had done so? Some obvious problems:
2038 is not going to be disaster, unless too many will think that just upgrading to a 64 bit time_t will magically solve all problems. (If it were that simple, we could have let localtime() return a 4 digit year to avoid Y2K.) Some time ago, I saw the timetable SUN is going to use to introduce a 64 bit time_t value. It's going to be a 10+ year traject. Abigail
In Section
Seekers of Perl Wisdom
|
|