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: 1108a1,37e6dbf5e31f6da0
X-Google-Attributes: gid1108a1,public
X-Google-Thread: ff6c8,37e6dbf5e31f6da0
X-Google-Attributes: gidff6c8,public
X-Google-Thread: 10db24,37e6dbf5e31f6da0
X-Google-Attributes: gid10db24,public
X-Google-Thread: 103376,37e6dbf5e31f6da0
X-Google-Attributes: gid103376,public
X-Google-Thread: f43e6,37e6dbf5e31f6da0
X-Google-Attributes: gidf43e6,public
From: tmoran@bix.com
Subject: Re: Software Engineering News Brief
Date: 1996/11/07
Message-ID: <55tipm$161@news2.delphi.com>#1/1
X-Deja-AN: 195135468
organization: Delphi Internet Services Corporation
newsgroups: 
 comp.lang.ada,comp.sw.components,comp.object,comp.software-eng,comp.edu
Date: 1996-11-07T00:00:00+00:00
List-Id: <comp.lang.ada>


>  I don't believe there is any requirement to *limit* years to 1900-2099,
>rather there *is* a portability requirement to allow *at least* that range.
   I just looked this up and it needs correction: the system should be
able to raise an exception when the year is outside 1901 through 2099,
or the month is outside 1 through 12, etc.  If the vendor wants to allow
the programmer to relax these rules, he'll have to allow the programmer
to do it via a pragma, compilation time switch, or some such thing, and,
of course, the vendor should then document just what his compiler allows.