Re: Ada95 to ANSI_C converter

[jsa@alexandria (Jon S Anthony)]

In article <5hvjb7$7us$1@gail.ripco.com> xanadu@ripco.com (Jennifer E. Lee) writes:

> Jon S Anthony <jsa@alexandria> wrote:
> >  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.

OK - that's some new information.


> >  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.

OK, it sounds as if the important part here is that everything has to
run on the HPBS.  In particular, the customer's code.


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

Sure, but that in itself is not a problem.  It's a problem if BOTH

i. It only lives on HPBS (I'm sure you are saying this is true)
and
ii. You can't talk to the HPBS from another box

Is ii. true???  If not (that is you _can_ talk to the HPBS from
another box), then you may yet be in luck.


> >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.

But, I think you are saying this library also only lives on HPBS.
Correct?


> >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.)

So the picture is:

  +------------------+
  |  Box Running     |
  |  Client Ada95    |
  |  network system  |======> Normally hooked to SDH/ATM/SONNET network
  |  application     |	      (presumably this box has drivers for this
  |  code            |	       network "card")
  |                  |
  +------------------+

For testing you want to have:

  +------------------+	      +------------------+
  |  Box Running     |	      |  Your Box (based |
  |  Client Ada95    |	      |  on HPBS)      	 |
  |  network system  |	      |  emulating the   |
  |  application     |=======>|  SDH/ATM/SONNET  |
  |  code            |        |  network         |
  |                  |        |                  |
  +------------------+        +------------------+

Or do you really want:

  +----------------------------------------+
  |  Your Box (based on HPBS) running BOTH |
  |  your emulation code for ATM/SONNET    |
  |    AND				   |
  |  Client Ada95     			   |
  |  network system   			   |
  |  application      			   |
  |  code             			   |
  +----------------------------------------+

Which of these last two pictures is accurate for your situation??


> >  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.

Yes, but that is just out of the box Ada95 so if you have your cross
compiler you are done.  The linker will take care of the rest.

/Jon
-- 
Jon Anthony
Organon Motives, Inc.
Belmont, MA 02178
617.484.3383
jsa@organon.com