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: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: C interface - Apex/Verdix
Date: 1997/06/07
Message-ID: <dewar.865692880@merv>#1/1
X-Deja-AN: 246810828
References: <338ce5d2.87925678@news.mhv.net> <5mjb0u$dhi@newshub.atmnet.net>
 <3395DC9F.3A25@lmco.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-06-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Gary says

<<I am coding in Ada95 (for the first time) using the Apex Ada 2.2.3A
compiler and need to interface with C/C++ code compiled using the Sun
compiler.  I am able to link a main Ada program with a C procedure using
the pragma Import but I have to supply the "mangled" C linker_name.  To
get this name I have to use the UNIX "nm" command on the object file. 
This seems dangerous if the C compiler ever decides to change the way
this "mangled" name is generated.  Do you know of a better way around
this?  My platform is Sun Solaris 2.5.1.  Can I use this VADS language
package and if so, where is it?
>>

This kind of manual mangling is not required in Ada 95 to interface with
C code. Assuming you have a full language implementation that supports
C as a language name in Import, then using the name as it is used in
the C program as the External_Name parameter (as opposed to the Linker_Name)
must work correctly. If it does not, then this is a clear bug that should be
reported to the vendor.