So we have a Y2.031K problem at the end of this year {at least for 30 year
mortgage calculating programs}.
I'm still not over the original y2k. The world is coming to an end -
again!!!
.......
Sorry, I digressed. It was a hell of a Monday and if I could only worry
about this ..... Well back to reality
--------------------------------------------------------------------
Gary Gorsline
Easy Business Software
========================== End of Message ==========================
----- Original Message -----
From: "Richard Burmeister" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Monday, August 13, 2001 2:29 PM
Subject: RE: TimGetSeconds in year 2036?
> > From: Erik Blake
>
> > Since time is stored as a UInt32 number of seconds since
> > Jan1, 1904, the return value will roll over sometime in
> > 2036 - a few years after I retire :)
>
> Yup. Prefs won't let you enter anything past 12/31/2031.
>
> > 2036 is, I admit, a fair ways off, but we all know that
> > code has a habit of staying around longer than expected.
> > Any thoughts?
>
> I expect things will have to change before then.
>
> > I'm curious as to the datum chosen - why not Jan 1, 1970
> > like C (at least the Borland implementation)? That will
> > last until the 22nd century - I'll be dead :(
>
> Sorry to hear about your impending demise. You can blame it on that Apple
> cult. (no serious offense meant)
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
