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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c4cb2c432feebd9d X-Google-Thread: 1094ba,c4cb2c432feebd9d X-Google-Attributes: gid103376,gid1094ba,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!ken-transit.news.telstra.net!lon-in.news.telstra.net!news.telstra.net!news-server.bigpond.net.au!53ab2750!not-for-mail From: "robin" Newsgroups: comp.lang.ada,comp.lang.fortran References: <0ugu4e.4i7.ln@hunter.axlog.fr> <%P_cg.155733$eR6.26337@bgtnsc04-news.ops.worldnet.att.net> <2006052415345816807-gsande@worldnetattnet> Subject: Re: Ada vs Fortran for scientific applications X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: <5H9dg.10257$S7.8193@news-server.bigpond.net.au> Date: Thu, 25 May 2006 03:40:49 GMT NNTP-Posting-Host: 144.134.49.43 X-Complaints-To: abuse@bigpond.net.au X-Trace: news-server.bigpond.net.au 1148528449 144.134.49.43 (Thu, 25 May 2006 13:40:49 EST) NNTP-Posting-Date: Thu, 25 May 2006 13:40:49 EST Organization: BigPond Internet Services Xref: g2news2.google.com comp.lang.ada:4440 comp.lang.fortran:10228 Date: 2006-05-25T03:40:49+00:00 List-Id: "Ed Falis" wrote in message news:op.s92jl8t85afhvo@dogen... > On Wed, 24 May 2006 14:34:58 -0400, Gordon Sande > wrote: > > > The urban legends have the Fortran error of a DO loop that changed into > > an assignment because of a typo changing a comma into a period and > > a satellite was lost. For Ada it is a tossed interrupt that caused a > > launch failure. Bad practice of one will always be inferior to good > > practice of the other. > > In the Ariane 5 case, it wasn't the language, but mismanagement in > applying software appropriate to a launcher with different flight > parameters to a new one without review. That wasn't the case. The code was reviewed, and it was decided that the particular conversion didn't require a check for overflow (even though similar conversions in the vicinity had protection). (This was a conversion from float to 16-bit integer). Anyone experienced with real time programming would have pointed out that it was a stupid thing to do.