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.6 required=5.0 tests=BAYES_40,FREEMAIL_FROM,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,37e6dbf5e31f6da0
X-Google-Attributes: gid103376,public
From: jimgregg@aol.com
Subject: Re: Software Engineering News Brief
Date: 1996/11/05
Message-ID: <19961105175300.MAA11951@ladder01.news.aol.com>#1/1
X-Deja-AN: 194664934
sender: news@aol.com
references: <55nqea$32a@news2.delphi.com>
organization: America Online, Inc. (1-800-827-6364) (1.10)
newsgroups: comp.lang.ada
Date: 1996-11-05T00:00:00+00:00
List-Id: <comp.lang.ada>


>The standard says nothing about external, human readable 
>input/output formats, however, and as an international 
>standard it could hardly demand conformance to, say, 
>"MM/DD/YY" or "Fifth Day of November, Year of Our
>Lord Nineteen Hundred and Ninety Six".  ;)

So if you are using a package that provides utility subprograms
for converting between Calendar.Time and "mmddyy", check the
implementation.  It may use 1900 in conversion expressions.

I have a package called DATES, provided by a compiler vendor, 
that has this problem.  

Jim Gregg
Software Compositions