TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show HTML 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]>
X-To: "Allen, Stephen" <[log in to unmask]>
Date: Wed, 25 Nov 1998 14:57:07 -0500
Reply-To: "Robert I. Eachus" <[log in to unmask]>
From: "Robert I. Eachus" <[log in to unmask]>
In-Reply-To: <AD85D970A1CDD11186D100AA004A095A1E0979@XCGCA040>
Content-Type: text/plain; charset="us-ascii"
Parts/Attachments: text/plain (26 lines)
At 01:44 PM 11/24/98 -0800, Allen, Stephen wrote:
>My employer, Logicon, Inc. (http://www.logicon.com/
><http://www.logicon.com/> ) has a need to convert a legacy ADA 83 system to
>C/C++. Since this conversion project is already committed, I would
>appreciate your response should you know of any product or services that
>could be of help.

   Are you looking for a referral to a good psychiatrist, or a new job?

   Seriously, I have used C++ and Ada, and tried to convert both ways.
Converting C++ into Ada is not hard, but the reverse is very painful.  The
problem is not with any of the strengths or weaknesses, as such, of either
language, but with overloading.  In some areas you will have several
subprogram calls per line where you have to resolve WHICH operator or
function is (or should be) called.

   It might be worth using ASIS to design a tool to unambiguously resolve
every call in the source.  But if you are going that far, it is far easier
to convert the Ada 83 to Ada 95 and have done.

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...

ATOM RSS1 RSS2