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: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Simple ADA/C Question Date: 1997/03/06 Message-ID: <1997Mar6.124303.1@eisner>#1/1 X-Deja-AN: 223587136 X-Nntp-Posting-Host: eisner.decus.org References: <01bc23b2$ecc64960$64e2b8cd@p5120.bda> <331c6ca7.792732@news.demon.co.uk> X-Nntp-Posting-User: KILGALLEN X-Trace: 857670188/2129 Organization: LJK Software Newsgroups: comp.lang.ada Date: 1997-03-06T00:00:00+00:00 List-Id: In article , kst@sd.aonix.com (Keith Thompson) writes: > No, I don't know of any Aonix or other compiler for which Integer and > Interfaces.C.int have different representations, but then I'm not very > familiar with our Intel products. I would hope Aonix would look to supporting additional platforms in future years, and there is always the possibility that on one of them a dominent C compiler could have a different integer size than was appropriate for ObjectAda (I boldly use that name claiming that Aonix has more than used up their quota of name changes for the lifetime of the Ada95 standard :-). < from Robert Dewar > >> As for Keith's guess that there could be C compilers that disagree on >> int size, I doubt it. Keith are you aware of all the discussions going >> on around C sizes on 64-bit machines? The fact that a C compiler is dominant may be less related to whether it supports the rumored forthcoming consensus and more related to whether it has the Microsoft brand. Larry Kilgallen