Xref: utzoo comp.sys.ibm.pc:30718 comp.sys.atari.st:17419
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!zephyr!tektronix!percival!bucket!leonard
From: leonard@bucket.UUCP (Leonard Erickson)
Newsgroups: comp.sys.ibm.pc,comp.sys.atari.st
Subject: Re: Will Your SW Make it to the year 2000?
Message-ID: <1501@bucket.UUCP>
Date: 27 Jun 89 23:35:39 GMT
References: <4342@druhi.ATT.COM>
Reply-To: leonard@bucket.UUCP (Leonard Erickson)
Organization: Rick's Home Grown Unix; Portland, OR
Lines: 22

In article <4342@druhi.ATT.COM> terrell@druhi.ATT.COM (TerrellE) writes:
<Will your software make it into the 21st century?  Does it cope with the
<Gregorian calendar reform of the 16th century?
<
<I was amused to find that allegedly state of the art scheduling software, 
<TimeLine, is broken for the year 2000.  So is MS DOS.
<
<The Gregorian calendar reform makes every year evenly divisible by 4 a
<leap year EXCEPT for century years.  Consequently there is no January 29,
<2000.

Sorry, but you got it wrong. Century years are leap years if they are
evenly divisible by 400! 1900 wasn't a leap year (but several programs
like Lotus and dBase think it was!) 2000 is a leap year. And MS-DOS avoids
the problem by stopping at midnight Dec 31, 2099.

Repeat, there *is* a Feb 29 in the year 2000.
-- 
Leonard Erickson		...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters." -- Solomon Short