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,90f687f65a66617e
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Simple ADA/C Question
Date: 1997/03/02
Message-ID: <dewar.857350486@merv>#1/1
X-Deja-AN: 222627739
References: <Pine.LNX.3.95.970225100418.10492A-100000@vf700f.msfc.nasa.gov>
 <01bc23b2$ecc64960$64e2b8cd@p5120.bda>
 <Pine.LNX.3.95.970226082729.7991A-100000@vf700f.msfc.nasa.gov>
 <dewar.856972571@merv> <E6BCJK.2LL@thomsoft.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-03-02T00:00:00+00:00
List-Id: <comp.lang.ada>


Keith said

<<If you have a C function that returns an int, the corresponding Ada
function's return type should be Interfaces.C.int.  Yes, C's int and Ada's
Integer are usually the same size, but why take chances when the language
provides a type that's *guaranteed* to have the same representation?>>

I understand that position, but the trade off is between piles of annoying
conversions and much more straightforward code in some instances.

However, this was not the issue, Bob said that using int on the C side
and Integer on the Ada side definitely *will* cause problems, and this
is plain wrong!

Are there any compilers incidentally where int in C is not the same
as Integer in Ada? Certainly int = Integer on all GNAT compilers.
Hard to believe that anyone would deviate from this equivalence. Given
that the choice of what Integer means in Ada is definitely implementation
dependent, it seems foolish to make any other choice.