2038, and it's more a Unix problem than a C problem.
Unix states the date as the number of seconds since the beginning of 1970.
Simply, after some time in 2038, a 32 bit variable can not hold that
many seconds.  64 bit machines will have the year 20 quadrillion problem
or something.  :-)

TomG

>The next date-related problem, IIRC, is in 2034 - something to do with
>C/C++'s common date function overflowing. And following that, maybe some
>software peeps will make the same mistake of presuming "20", and 2100
>will be a problem.
>
>McMac
>I used up all my sick days, so I'm calling in dead.
>
>_________________________________________________________________
>Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
>Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

PGP signature

Reply via email to