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,d4c93107c9fcba15
X-Google-Attributes: gid103376,public
From: Gautier <Gautier.deMontmollin@maths.unine.ch>
Subject: Re: ADA V3.5 on ALPHA platform
Date: 1999/12/10
Message-ID: <385150D8.8E069881@maths.unine.ch>#1/1
X-Deja-AN: 559101108
Content-Transfer-Encoding: 7bit
References: <38512EE7.B0241FFA@unnecessary.csc.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-12-10T00:00:00+00:00
List-Id: <comp.lang.ada>

Wow! Your bug runs nice (DEC Ada 3.5-2)...

%ACS-I-CL_LINKING, Invoking the OpenVMS Linker for OPENVMS_AXP target
$ ru bug
INTEGER'VALUE ("-") returns  0

There is another one, very strange: in my multi-precision library,
there is a constant boolean (DEBUG) that cause testings on multi-numbers,
only with a call to a Test function with an `in' parametre. It is
algorithmically neutral.

With DEBUG=true or no `suppress_all' pragma, the decimals of pi
(Test_int.adb) are calculated correctly. With DEBUG=false and
suppress_all on, the decimals of Pi are not calculated correctly at all
(instead of 1000 decimals, you obtain numbers like -172348687, which
is a slightly inaccurate approximation...). 

You can test it using
  http://members.xoom.com/gnatlist/multi002.zip

I suspect the optimizer... (case signaled to Compaq).

Otherwise I find DEC Ada an excellent compiler (at least
in terms of efficiency!)

-- 
Gautier

_____\\________________\_______\
http://members.xoom.com/gdemont/