Re: Ada95 to ANSI_C converter

[xanadu@ripco.com (Jennifer E. Lee)]

Jon S Anthony <jsa@alexandria> wrote:
>I'm not Phil, but I am now getting the drift of what you are up
>against.  Let me recap to see if at least the problem is now "clear":
>
>  1. HPBS apparently only has a C compiler targetting it.

CORRECT.

>  2. There is (apparently) no way to communicate with the HPBS from
>     another subsystem (which could have a board or some such which
>     does have something more than a C compiler - in particular an
>     Ada95 compiler.)

No, it doesn't. HPBS is an off the shelf validation device which can
emulate our client's SDH/SONNET/ATM network. Our client do not want
us to integrate our codes with their network system softwares.

>  3. Whatever it is that needs to be accomplished, the end result must
>     _run_ on the HPBS (probably because of 2 or 2 plus some other
>     reasons).

Indeed. That's called "INFORMATION HIDING." They want us to validate
their Ada codes through our HPBS.

>It sounds as if 1. is definitely true at the moment.  Is 2 really
>true?  I find this somewhat hard to believe (as a variety of control
>systems that I am aware of support this sort of thing).  If 2. really
>is true then 3. would seem to follow automatically.
>
>Now, if 2. is true (and thus 3), Ada.Interfaces is not going to help
>you and Phil's suggestion is, unfortunately, not viable.

You are right. Please notice, the we have to use HP's C function
library to call up the HPBS' manager program.

>If 2. is _not_ true, then the "other subsystem which can communicate
>to the HPBS" must have a library supplied for it which allows this
>communication (this is standard for the sort of control systems I
>mentioned above).  Presumably
>
>a) this library's source would be in C, as you folks would be the ones
>supplying it for your product!

Again, a good understanding of my question.

>b) your customer's Ada95 code is running on this thing (which implies
>that it _does_ have an Ada95 compiler for it) as why else would they
>believe that they could even use your product.

No, their Ada codes are for their network system applications only.
However, they need to send cell through the ATM/SONNET networks via
our BOX (can not tell you the name; it's a MUX.)

>If a) and b) are true, then you are in luck and Phil's suggestion will
>work like a charm.  Just use Ada.Interfaces to write an abstracted
>interface to your library.  There is no problem in having OO Ada95
>call out to your non-OO C.  Works fine.

a.) is true, bur b.) is not.

>Going back to the case of 2. being true (and thus a) and b) are
>irrelevant), then we come to the following sort of possibilities:
>
>  I.  Get some Ada95 to C compiler whose output will compile under the
>      C compiler you have for the HPBS.  Maybe ICC's will work.
>
>  II. Get someone (Aonix or ACT) to provide an Ada95 cross compiler to
>      the HPBS (effectively giving the HPBS an Ada95 compiler).

No, we want an Ada cross complier which can embeded c function in it.

>The other possibility (which you mention) of recoding the Ada95 into C
>is, IMO, much more expensive than either I or II and _far_ more risky.

Indeed.

>Am I now correctly understanding the situation???

Very much, thank you. :^)
--
Love, Jennifer Ellen Lee                              (xanadu@ripco.com)
~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~@>*---~
I love life, I need food, but I'd rather die without democracy.
 "Ren Min Er Nu:, Shi De Ren Min." -- Wang Dan 1989