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,ef667ac6a3e5446b X-Google-Attributes: gid103376,public From: "David C. Hoos, Sr." Subject: Re: Sun Ada 3.0 / 2.1.1 Date: 1999/05/18 Message-ID: #1/1 X-Deja-AN: 479376654 Content-Transfer-Encoding: 7bit References: <37408CC0.5E601B20@sll.northrop.com> X-Priority: 3 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-MSMail-Priority: Normal MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-05-18T00:00:00+00:00 List-Id: Guy Calinsky wrote in message news:37408CC0.5E601B20@sll.northrop.com... > > I have a requirement to upgrade my project's compiler from Sun Ada 2.1.1 > to Sun Ada 3.0. > Easy enough, except that my application makes several calls to C > functions, passing floating point numbers. > Whereas my application worked fine under 2.1.1, the floating point > numbers are not mapping correctly between 3.0 and C and I get junk for > results. Does anybody know why this is? > Sun and Rational are being difficult. > My guess would be that your code has interfaces to C based on types from the compiler's package Standard which have changed size. For example, I remember that VADS on the SGI IRIX platform changed their type Float from 32-bit to 64-bit, and the Oracle interface was based on equating C float to VADS Float, and C double to VADS Long_Float. You should have your own project-specific types of fixed size, to protect yourself from compiler changes. Of course Ada95 makes this much easier with the package Interface, and its child Interfaces.C -- providing types which are specifically equivalent to corresponding C types.