Xref: utzoo comp.sys.ibm.pc:30735 comp.sys.atari.st:17433
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cmcl2!rna!amms4!hjg
From: hjg@amms4.UUCP (Harry Gross)
Newsgroups: comp.sys.ibm.pc,comp.sys.atari.st
Subject: Re: Will Your SW Make it to the year 2000?
Message-ID: <381@amms4.UUCP>
Date: 28 Jun 89 02:57:44 GMT
References: <4342@druhi.ATT.COM>
Reply-To: hjg@amms4.UUCP (Harry Gross)
Organization: Eagle Clothes, Inc., New York, NY
Lines: 32

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?
	[stuff deleted]
>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.

Um - that ought to be February :-)  By the way, the proper determination
is just a wee bit more than that stated above.  Specifically, a leap year
exists if:

		1) the year is divisible by 4 AND
		2) the year is NOT divisible by 400

thus, the years 1700, 1800 and 1900 were leap years, but 2000 will NOT be
a leap year, and 2100 WILL be.

On the other hand, does anyone really expect their software to be up and
running in the year 2100? :-)

By the same token, I expect that DOS will have been replaced by something
else by the year 2000 (perhaps DOS 9.8 :-) and Microsoft and IBM will no
doubt have fixed the problem in that release :-)


-- 
		Harry					 |  reserved for
							 |  something really
Internet: hjg@amms4.UUCP   (we're working on registering)|  clever - any
UUCP: {jyacc, qtny, rna, bklyncis}!amms4!hjg		 |  suggestions?