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,df90a4053dcaf2ca,start
X-Google-Attributes: gid103376,public
From: "K. E. Garlington" <Kennie.E.Garlington@nospam.lmco.com>
Subject: Exception on System.Max_Digits
Date: 1998/01/30
Message-ID: <34D20EC6.55DD@nospam.lmco.com>#1/1
X-Deja-AN: 320614422
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Organization: Lockheed Martin Tactical Aircraft Systems (LMTAS)
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-01-30T00:00:00+00:00
List-Id: <comp.lang.ada>


We have a case where two Ada83 compilers provide different results, and
we are trying to decide which is correct.

Both compilers have System.Max_Digits = 15. When we use Float_IO
to read the number

   -2627.097925618800

one vendor raises a Constraint_Error, the other doesn't. The vendor
of the compiler raising the error says that it is because the number
has too many digits; removing the final zero causes the exception to
be avoided. The other vendor accepts the number.

Is either vendor wrong?

Also, will System.Max_Digits apply to any floating-point type?