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
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Exception on System.Max_Digits
Date: 1998/02/01
Message-ID: <dewar.886368148@merv>#1/1
X-Deja-AN: 321166596
References: <34D20EC6.55DD@nospam.lmco.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 886368300 22055 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-02-01T00:00:00+00:00
List-Id: <comp.lang.ada>


Ken asks

<<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.
>>

A truly surprising bug, it is of course the case that input numbers can
have any number of digits (and having to handle this in Float_IO can
be a bit annoying). The ACVC certainly tests for this, so I guess the
compiler which raised Constraint_Error must not be validated???