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: Simon Wright Subject: Re: Sun Ada 3.0 / 2.1.1 Date: 1999/05/22 Message-ID: #1/1 X-Deja-AN: 481188487 X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98 References: <37408CC0.5E601B20@sll.northrop.com> X-Trace: news.demon.co.uk 927472670 nnrp-10:19990 NO-IDENT pogner.demon.co.uk:158.152.70.98 Organization: At Home Newsgroups: comp.lang.ada X-Complaints-To: abuse@demon.net Date: 1999-05-22T00:00:00+00:00 List-Id: Guy Calinsky writes: > 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. I don't _know_ why, but could it be that the old Ada used double and the new uses float? or vice versa? How have you declared the floating point numbers in Ada? (sometimes the actual type used depends on your declared range). -- Simon Wright Work Email: simon.j.wright@gecm.com Alenia Marconi Systems Voice: +44(0)1705-701778 Integrated Systems Division FAX: +44(0)1705-701800