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,c615e41a65104004 X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: Size code Ada and C Date: 1998/07/07 Message-ID: #1/1 X-Deja-AN: 369303821 References: <35921271.E51E36DF@aonix.fr> <6mtiv0$9j3@gcsin3.geccs.gecm.com> <6n8393$hoi$2@platane.wanadoo.fr> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1998-07-07T00:00:00+00:00 List-Id: In article dewar@merv.cs.nyu.edu (Robert Dewar) writes: > I am puzzled, I thought the problem derived from a constaint error > that was raised by a fixed point operation ... There was a floating to fixed/integer conversion instruction in hardware, that signaled a fault because the operand was out of range. This could have been handled by a local (Ada) exception handler. However, the decision was made that this situation could only occur (in the Arianne 4) in the case of a hardware failure. So the exception was allowed to propagate to an outermost handler that switched control to the backup and dumped state. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...