TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
"W. Wesley Groleau x4923" <[log in to unmask]>
Thu, 3 Jun 1999 12:48:43 -0500
"W. Wesley Groleau x4923" <[log in to unmask]>
text/plain (25 lines)
> So far, my informal search has revealed none, except for one possible,
> > unconfirmed Ada '83 Verdix library, which quite possibly may not have been
> > written in Ada.
> >
> There is a known problem with the VADS dates package.  This package
> provides textual I/O routines for date values.  If you entered a
> 2 digit year number then it always assumed the twentieth century
> (ie: 19xx).
> We have a corrected version of this package available through our
> support organization.  The new version allows you to specifiy a sliding
> window to define which century to add to a 2 digit year.
> Please note that this package was never used inside VADS.  The dates
> package was provided for use by our customers.  VADS uses operating
> sytem routines for obtaining date/time information and encoding it
> for storage.  Because of this Rational cannot provide a Y2K guarantee
> on any platform that is itself not Y2K compliant.

So, the only known (on this list at least) Y2K problem in Ada is one
package written for customers that WANTED the problem.  :-)

Anyone know of any Y2K problems in Java?  That would be amusing negative
publicity, especially since Java was invented _after_ Y2K hit the news.