TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version: 1.0
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Chad Bremmon <[log in to unmask]>
Date: Mon, 8 Mar 1999 18:56:27 -0500
Content-type: text/plain; charset=us-ascii
Reply-To: Chad Bremmon <[log in to unmask]>
Parts/Attachments: text/plain (21 lines)
I started this thread and I guess I had better re-explain myself.

What I was thinking of was the fact that had I written my Ada code with
Non-magic numbers:

type Year_type is range 70 .. 99;

I could easily modify that to be

type year_type is range 1970 .. 1999;

I may of course have to make some modifications to my IO routines that have
written the 2 digit numbers to files.

I guess maybe a survey would be more appropriate. . . how many ada programs are
struggling because of the Y2K problem?

How many were easily able to fix it in isolated areas of their code?