TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Proportional Font
Show Text 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, 9 Sep 1999 13:53:03 -0500
"W. Wesley Groleau x4923" <[log in to unmask]>
text/plain (27 lines)
> A program to convert C header files to Ada packages is, in my opinion, a
> critical need for gaining acceptance of Ada.  The argument "It is too hard
> to switch back and forth to convert by hand; I'll just use C" is too
> compelling.

Writing 1,000 lines of C might be better than writing 500 lines of Ada
plus 1,000 lines of Ada binding.  But the argument degenerates from "too
compelling" to "too stupid" when one uses it to justify writing 6,000
lines of C instead of 3,000 lines of Ada and a KSLOC Ada binding.  (Is the
typical Ada binding even that big?)

> The program "c2ada" seems to be the only available tool for this purpose.
> But there is seemingly no vendor support for this tool (if I am wrong,
> please correct me).  Why is this the case?
> I have not been able to get the tool to work.  I could understand the lack
> of need for support if the tool was trivial to use and had no bugs.  But
> unless I am making some really simple mistake (always possible), it is not
> trivial to use correctly.

The c2ada Web page at Intermetrics listed Python and some other things as
prerequisites.  Python downloaded and built as per instructions, and
seemed to work.  But all the other prerequisites failed to even build when
I followed their instructions.  Had to find one of them by Web search
because the hyperlink was stale.

But, you get what you pay for.  :-)