TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
"W. Wesley Groleau x4923" <[log in to unmask]>
Date:
Fri, 5 May 2000 09:13:34 -0500
Reply-To:
"W. Wesley Groleau x4923" <[log in to unmask]>
Parts/Attachments:
text/plain (16 lines)
> The standard package Ada.Calendar defines a type Time whose
> internal implementation isn't specified by the language, but
> currently (1995 edition of Ada) you can only access years in
> the range 1901 .. 2099 for this type.

How can/does the validation suite test this?  You certainly can't change
the O.S. date to 2039!  Some compilers (I can't say how many) just use the
O.S. time format for their private Calendar.Time

But of course in 2037, they'll warn us the end of the world is soon, and
in 2039 we'll have forgotten all about it.

--
Wes Groleau
http://freepages.genealogy.rootsweb.com/~wgroleau

ATOM RSS1 RSS2