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,355f90547d1b4b5 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: PRECOMPILATION Date: 1999/02/10 Message-ID: <36c20a62.18186185@news.pacbell.net>#1/1 X-Deja-AN: 443154835 References: <918556681.260459@dedale.pandemonium.fr> <1999Feb9.081125.1@eisner> <36C08503.510FE86B@magic.fr> <36c0c9f7.6074742@news.pacbell.net> <36C1E967.A1A0232F@magic.fr> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.pbi.net 918686558 206.170.2.129 (Wed, 10 Feb 1999 14:42:38 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Wed, 10 Feb 1999 14:42:38 PDT Newsgroups: comp.lang.ada Date: 1999-02-10T00:00:00+00:00 List-Id: >As an example, just consider that a file size, of type "long" in C, can >be >implemented on 32 or 64 bits, depending on the operating system. And when it's passed from a 64 bit system to a 32 bit system what happens to the extra 32 bits? Or do you mean that sometimes the Ada code talks to some C code that expects 32 bits, and other times the same Ada must talk to a differently compiled version of the same C code, but one that expects 64 bits? In which case, why not standardize on the Ada 32 bits (using a rep clause) and do the usual preprocessor stuff for making a C program "portable"?