At 13:39 2001/08/13 -0700, you wrote:
> > Prefs won't let you enter anything past 12/31/2031.
>
>The year field in DateType is an unsigned 7 bit numbers counting from 1904,
>so the last year we can represent in 2031. DateTimeType uses a full 16 bits
>for the year, so it's not a problem. According to my crude calculations,
>TimGetSeconds and other functions that use an unsigned 32 bit number to
>count seconds from the start of 1904 will all run out around 2040.
>
>Clearly, we'll have to do something about these limitations sometime well
>before 2031. We've got about 20 years if we want to allow people to schedule
>stuff 10 years ahead. In the meantime, if you need to deal with dates in the
>distance past or future, you'll have to write your own functions rather than
>using the ones provided by the OS.
Hmmm, I can just imagine some folks sitting around in 1970 or 1980 saying
the same thing about year 2000.
I'm curious as to why a new operating system/platform, with little reliance
on legacy code, would be hamstrung like this - if things go the way Palm
wants them to, I'm sure there will be plenty of problematic legacy Palm OS
code in 30 years time.
Erik Blake
-------------------------------------------------------------------
Icefield Tools Corporation tel: (867) 633-4264
PO Box 30085 fax: (867) 633-4217
Whitehorse, Yukon CANADA e-mail: [EMAIL PROTECTED]
Y1A 5M2 internet: http://www.icefieldtools.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
