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,544e7f5698c48b7c X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: precise floats Date: 1998/08/07 Message-ID: #1/1 X-Deja-AN: 378740002 References: <6q7vtb$jk$1@heliodor.xara.net> <6q8afs$5aq$1@usenet.rational.com> <6q8b4a$5cu$1@usenet.rational.com> <6qco5r$v8n$1@nnrp1.dejanews.com> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 902463007 12649 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-08-07T00:00:00+00:00 List-Id: <> The annex B requirements are perfectly clear, if Interfaces has no floating-point types, this is valid only if the hardware does not support floating-point at all. So this is most certainly a bug.