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.2 required=5.0 tests=BAYES_00,FROM_WORDY, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,dec0a6ed5b5044de X-Google-Attributes: gid103376,public From: "Nick Roberts" Subject: Re: Code portability question Date: 1999/01/31 Message-ID: <794u48$snh$4@plug.news.pipex.net>#1/1 X-Deja-AN: 439447884 References: <36A94B78.963F3215@wvu.edu> <36AAC327.CA9A81ED@wvu.edu> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: UUNET WorldCom server (post doesn't reflect views of UUNET WorldCom) Newsgroups: comp.lang.ada Date: 1999-01-31T00:00:00+00:00 List-Id: One thing is for sure: if the UNIX target is not an IA (Intel Architecture) machine, then whether the PC's CPU is a K6 or other IA is irrelevant. Otherwise (if both are IA), it is faintly possible that the flags for the NDP (floating-point unit) are set differently on the UNIX machine cv the PC, and this is causing problems. But one other, more likely, possible cause occurs to me: does your friend's program write out floating-point data into a data file, and then read it back in again? If so, and your friend decided to simply copy the data file from PC to UNIX, then this might explain the problems! ------------------------------------------- Nick Roberts -------------------------------------------