From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ed926d4d933b76e3
X-Google-Attributes: gid103376,public
From: Mark Bennison <mark.bennison@gecm.com.no.spam>
Subject: Re: C interface - Apex/Verdix
Date: 1997/05/30
Message-ID: <5mmoe8$dq4@gcsin3.geccs.gecm.com>#1/1
X-Deja-AN: 244976933
References: <338ce5d2.87925678@news.mhv.net> <5mjb0u$dhi@newshub.atmnet.net>
Organization: GEC-Marconi Radar & Defence Systems Ltd
Newsgroups: comp.lang.ada
Date: 1997-05-30T00:00:00+00:00
List-Id: <comp.lang.ada>


cgreen@yosemite.atc.com (Christopher Green) wrote:
>In article <338ce5d2.87925678@news.mhv.net>,
>Paul Van Bellinghen <pvanbell@mhv.net> wrote:
>>Has anyone ever intefaced a C object module with an (Ada83) Ada
>>program in the Rational Apex or Verdix VadsCross environment? I am
>>planning to just include the object module in the compilation view and
>>use the  Pragma Interface (C, c-function-name). Will this work?
>
>You may also need pragma Interface_Name (c-function-name, "actual-name");
>this will account for situations where VADS name-mangling doesn't yield
>the correct name for the C function.
>

Another thing that may be relevant is that you will need ( in 
VadsCross, I haven't used Apex ) to add a WITH directive to the ada.lib 
file ( using a.info -i ) to give the location of your 'C' object code to 
the linker.

Mark.
-- 
Mark Bennison,           +-----------------------------------+
Technical Consultant,    | All opinions expressed are my own |
EASAMS Software Systems. +-----------------------------------+
"Death is a fickle hen, and random are her eggs" - Armando Iannucci
Remove '.no.spam' to return e-mail