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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8b9403e256f252f5 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-18 19:02:37 PST Path: bga.com!news.sprintlink.net!cs.utexas.edu!swrinde!gatech!bloom-beacon.mit.edu!panix!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody From: dewar@cs.nyu.edu (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Float to Fixed conversions Date: 18 Mar 1995 20:31:14 -0500 Organization: Courant Institute of Mathematical Sciences Message-ID: <3kg1h2$eqr@gnat.cs.nyu.edu> References: NNTP-Posting-Host: gnat.cs.nyu.edu Date: 1995-03-18T20:31:14-05:00 List-Id: Wayne Magor asks about conversion of float to fixed. The disparate behaviors of the two compilers he used are both correct. The number in question was a non-model number which lay between two modem numbers 0.0 and 1.0 (oops thats model numbers, although I rather like the idea of modem numbers :-) In this situation, either 0.0 or 1.0 is a valid result, there is no requirement for round-to-nearest (except in the case of Ada 95 decimal types, where rounding/truncation is indeed deterministic and well defined).