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
Show All Mail Headers

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

Print Reply
Subject:
From:
"Brashear, Phil" <[log in to unmask]>
Reply To:
Brashear, Phil
Date:
Fri, 5 May 2000 10:57:59 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
The conformity assessment ("validation") suite does not check this.
The tests involving Year_Number just check for correctness of range,
arithmetic operations,
relational operations, and the pre-defined functions of package
Ada.Calendar.

Philip W. Brashear
EDS Conformance Testing Center
4646 Needmore Road, Bin 46
P.O. Box 24593
Dayton, OH  45424-0593
(937) 237-4510
[log in to unmask]
http://www.eds-conform.com



> -----Original Message-----
> From: W. Wesley Groleau x4923 [mailto:[log in to unmask]]
> Sent: Friday, May 05, 2000 10:14 AM
> To: [log in to unmask]
> Subject: Re: C date package
>
>
> > 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