Hi
"Dev Teelucksingh" <[EMAIL PROTECTED]> wrote:
DT> This is a known problem with C which I discovered when researching
DT> the Y2K bug. The variable in C used to track the time (think it is the
DT> number of seconds elapsed since 1st Jan 1970) will roll over to 0 in
DT> 2038 (which the software of course thinks is 1st Jan 1970)
DT> So a lot of software written in C (which includes Linux or Eudora
DT> (see Eudora's Y2K page) ) will have this problem which includes
DT> Insight since it is written in Borland C.
DT> I am not sure if there has been any solution yet since everyone was
DT> working on Y2K.
Sure everybody has worked on Y2K ... Y2K was now, and this 'problem' will
be in 27.x years ...
AND if you recompile using a 64 bit intgere instead of 32 bits, you'll have
MUUUUUUUUUUCH time to use the software.
But to be absolutely honest I doupt that any program developed now will be
used in 30 years !
DT> Dev Teelucksingh
CU, Ricsi
--
Richard Menedetter <[EMAIL PROTECTED]> [ICQ: 7659421] {RSA-PGP Key avail.}
-=> Baby Philosophy - If it stinks, change it <=-
