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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c4cb2c432feebd9d X-Google-Thread: 1094ba,c4cb2c432feebd9d X-Google-Thread: 101deb,15c6ed4b761968e6 X-Google-Attributes: gid103376,gid1094ba,gid101deb,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!news3.google.com!news.glorb.com!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!mutlu.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada,comp.lang.fortran,comp.lang.pl1 Subject: Re: Ada vs Fortran for scientific applications Date: Tue, 11 Jul 2006 21:46:59 +0100 Organization: Pushface Message-ID: References: <0ugu4e.4i7.ln@hunter.axlog.fr> <%P_cg.155733$eR6.26337@bgtnsc04-news.ops.worldnet.att.net> <6H9dg.10258$S7.9150@news-server.bigpond.net.au> <1hfv5wb.1x4ab1tbdzk7eN%nospam@see.signature> <2006052509454116807-gsande@worldnetattnet> <1kzktalo9krea$.z8n9wev45xct$.dlg@40tude.net> NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1152650829 22866 62.49.19.209 (11 Jul 2006 20:47:09 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Tue, 11 Jul 2006 20:47:09 +0000 (UTC) Cancel-Lock: sha1:XiytUbg0LVi0rgfXeV6S4hzWLTo= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) Xref: g2news2.google.com comp.lang.ada:5628 comp.lang.fortran:11958 comp.lang.pl1:1995 Date: 2006-07-11T21:46:59+01:00 List-Id: "James Giles" writes: > Nor is initialization a very good solution. Well, unless > you have a value you can initialize with that's obviously > wrong (that's why IEEE has NANs). Initializing with > an arbitrary plausible value often conceals errors and > leads to plausible wrong answers. The Ada compiler we probably have in mind (GNAT) can: * set otherwise-uninitialised variables to an out-of-range value, where possible (eg, for a Boolean, set it to 255, since only 0 and 1 are legal values) * check validity even where the rules of the language would normally mean you don't need to, eg if a procedure takes a Boolean parameter, no need to check, because it has to be correct, right?!