Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!brl-adm!brl-smoke!brl-sem!ron
From: ron@brl-sem.ARPA (Ron Natalie <ron>)
Newsgroups: net.lang.c
Subject: Re: calculating leap years
Message-ID: <447@brl-sem.ARPA>
Date: Sun, 12-Oct-86 00:37:30 EDT
Article-I.D.: brl-sem.447
Posted: Sun Oct 12 00:37:30 1986
Date-Received: Sun, 12-Oct-86 13:45:20 EDT
References: <40@vianet.UUCP> <813@ethos.UUCP>
Distribution: net
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <813@ethos.UUCP>, ggw@ethos.UUCP (Gregory Woodbury) writes:
> The programs may not "need" to handle the dates beyond that 20 year interval
> but when the programs that are being written now hit the end of the century
> there are going to be a lot of installations and programs that are going
> to be suprised come "March 1" to see the computer say "Feb 28, 2000".
Eh?  You mean Feb 29?  Any computer that doesn't get the 28th right is really
ill.
> I had modified the comm system
> date routines to handle the 2000 non-leap year.
The year 2000 is a leap year.  Your code was more correct when it wasn't
modified.

-Ron