Xref: utzoo comp.sys.ibm.pc:30635 comp.sys.atari.st:17379
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!ralf
From: ralf@b.gp.cs.cmu.edu (Ralf Brown)
Newsgroups: comp.sys.ibm.pc,comp.sys.atari.st
Subject: Re: Will Your SW Make it to the year 2000?
Message-ID: <5325@pt.cs.cmu.edu>
Date: 27 Jun 89 03:40:06 GMT
References: <4342@druhi.ATT.COM>
Organization: Carnegie-Mellon University, CS/RI
Lines: 21

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 there IS a February 29, 2000.  Century years are not leap years
UNLESS they are evenly divisible by 400 (the calendar prior to the reform
gained about 3.2 days per 400 years).  However, lots of other software is
likely to break because the century is no longer 19.  For example, RFC 822
mail uses the year mod 100.  We'll have lots of fun with mailers trying to
figure out why the year is suddenly 00.
-- 
{harvard,uunet,ucbvax}!b.gp.cs.cmu.edu!ralf -=-=- AT&T: (412)268-3053 (school)
ARPA: RALF@CS.CMU.EDU     |"The optimist is the kind of person who believes a
FIDO: Ralf Brown 1:129/46 | housefly is looking for a way out."--Geo.J.Nathan
BITnet: RALF%CS.CMU.EDU@CMUCCVMA -=-=-=-=-=- DISCLAIMER? I claimed something?