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.2 required=5.0 tests=BAYES_00,FROM_LOCAL_HEX,
	FROM_STARTS_WITH_NUMS autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,7e8cebf09cf80560
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!news.glorb.com!feeder.erje.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Vinzent Hoefler" <0439279208b62c95f1880bf0f8776eeb@t-domaingrabbing.de>
Newsgroups: comp.lang.ada
Subject: Re: How would Ariane 5 have behaved if overflow checking were
 notturned off?
Date: Wed, 16 Mar 2011 23:27:47 +0100
Message-ID: <op.vsgjclzhlzeukk@jellix.jlfencey.com>
References: 
 <a8387564-0835-467d-a461-60a093c38133@k15g2000prk.googlegroups.com>
 <op.vscizsqqlzeukk@jellix.jlfencey.com>
 <4d80b140$0$43832$c30e37c6@exi-reader.telstra.net>
 <op.vsf7vmtblzeukk@jellix.jlfencey.com>
 <4d810172$0$4954$a8266bb1@postbox2.readnews.com>
 <d6e065fb-7271-42d5-812c-83912c8721a5@n1g2000yqm.googlegroups.com>
 <4d81231d$0$4966$a8266bb1@postbox2.readnews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Trace: individual.net w/isJPfK/1lPu860Gl5yWQ/L2cx7bDvjz1rbMn6jaybUYY+WJ6
Cancel-Lock: sha1:cRmeUAAjL+m778P6atZc5iG6ruo=
User-Agent: Opera Mail/11.01 (Win32)
Xref: g2news2.google.com comp.lang.ada:19240
Date: 2011-03-16T23:27:47+01:00
List-Id: <comp.lang.ada>

Hyman Rosen wrote:

> Why are we converting floats to 16-bit integers?

Because the CPU can handle integer much faster than the co-processor
can handle double precision floating point data.

> <http://web.archive.org/web/20000815230639/www.esrin.esa.it/htdocs/tidc/Press/Press96/ariane5rep.html>
> Recommendation R3 says "Do not allow any sensor, such as the inertial
> reference system, to stop sending best effort data." So if your sensor
> can report data over a certain range, you should probably not use a
> restrictive subtype that represents what you believe the possible
> observed range will be.

The question remains: What to do when you encounter an obviously fucked up value?


Vinzent.

-- 
A C program is like a fast dance on a newly waxed dance floor by people carrying
razors.
    --  Waldi Ravens