From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cfd23c10fd537a80
X-Google-Attributes: gid103376,public
From: Geoff Bull <gbull@acenet.com.au>
Subject: Re: Ada Calendar oddity <was Re: C date package>
Date: 2000/05/19
Message-ID: <3924B35E.DC0C9CDF@acenet.com.au>#1/1
X-Deja-AN: 625254548
Content-Transfer-Encoding: 7bit
References: <l0313030eb53d1408aee7@[144.205.16.58]>
 <39176D85.603D7AEC@research.canon.com.au>
 <39178DEA.FD2C20FA@research.canon.com.au> <8f92o1$6v$1@nnrp1.deja.com>
 <3918BB77.693C70D6@research.canon.com.au> <8fahfv$mgt$1@nnrp1.deja.com>
 <slrn8hioca.101.randhol+nospam@kiuk0156.chembio.ntnu.no>
 <wccn1lyjz94.fsf@world.std.com> <39230A82.CFA6E18D@earthlink.net>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@telstra.net
X-Trace: nsw.nnrp.telstra.net 958706727 203.35.118.1 (Fri,
 19 May 2000 13:25:27 EST)
Organization: Customer of Telstra Big Pond Direct
MIME-Version: 1.0
NNTP-Posting-Date: Fri, 19 May 2000 13:25:27 EST
Newsgroups: comp.lang.ada
Date: 2000-05-19T00:00:00+00:00
List-Id: <comp.lang.ada>



"Robert I. Eachus" wrote:
> 
> Robert A Duff wrote:
> 
> > The reason for the range 1901..2099 is that leap year calculations are
> > simpler (and more efficient) in this range -- in this range, all years
> > divisible by 4 are leap years (including 2000).  1900 and 2100 are not
> > leap years.
> 
>    True, but that was the reason it was that way in Ada 83, when
> avoiding the Y2K bug was a big deal. 

It was that kind of narrow (focussed on one problem) thinking
that led to the y2k bug!