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: eachus@spectre.mitre.org (Robert I. Eachus)
Subject: Re: Simple ADA/C Question
Date: 1997/03/03
Message-ID: <EACHUS.97Mar3133448@spectre.mitre.org>#1/1
X-Deja-AN: 222803215
References: <Pine.LNX.3.95.970225100418.10492A-100000@vf700f.msfc.nasa.gov>
Organization: The Mitre Corp., Bedford, MA.
Newsgroups: comp.lang.ada
Date: 1997-03-03T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <dewar.857350486@merv> dewar@merv.cs.nyu.edu (Robert Dewar) writes:

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

   Yes, and there is not much you can do about it...in the PC
environment for example there are C compilers with 16-bit ints, with
32-bits and compilers where the user gets to choose.

--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...