TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Jacob Sparre Andersen <[log in to unmask]>
Date: Fri, 5 May 2000 12:17:29 +0200
In-Reply-To: <000901bfb671$b80a36a0$3348fea9@mobileuser>
MIME-Version: 1.0
Reply-To: Jacob Sparre Andersen <[log in to unmask]>
Parts/Attachments: TEXT/PLAIN (29 lines)

> I have heard that the programming language "C"   will out
> grow its date package in I think 2030.
> I was wondering if there is any fact to this?

Sort of.

The year is 2038 iirc, and it is not as much a problem with
C as with the date handling functions in many Unixes.
Switching from a "32 bit compiler" to a "64 bit compiler"
shold delay this problem a few million years.

> and if Ada has any similar problems?

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.

I haven't read any articles on which problems we can expect,
when the range of years is changed.


"Any, sufficiently complicated, experiment is indistinguishable from magic."