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!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon06.news.prodigy.com!prodigy.net!newsdst02.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr14.news.prodigy.com.POSTED!4988f22a!not-for-mail
From: <adaworks@sbcglobal.net>
Newsgroups: comp.lang.ada,comp.lang.fortran,comp.lang.pl1
References: <mubcg.13522$fb2.853@newssvr27.news.prodigy.net>
 <epcs4e.qb8.ln@hunter.axlog.fr> <tHkcg.6937$kR6.484@trnddc05>
 <0ugu4e.4i7.ln@hunter.axlog.fr>
 <PkHcg.90575$Fs1.7198@bgtnsc05-news.ops.worldnet.att.net>
 <To_cg.10095$S7.4017@news-server.bigpond.net.au>
 <%P_cg.155733$eR6.26337@bgtnsc04-news.ops.worldnet.att.net>
 <6H9dg.10258$S7.9150@news-server.bigpond.net.au>
 <XVadg.76594$_S7.45873@newssvr14.news.prodigy.com>
 <1hfv5wb.1x4ab1tbdzk7eN%nospam@see.signature>
 <pan.2006.05.25.12.11.52.919554@linuxchip.demon.co.uk.uk.uk>
 <2006052509454116807-gsande@worldnetattnet>
 <R%dsg.63336$fb2.7555@newssvr27.news.prodigy.net>
 <bFesg.111860$mF2.27790@bgtnsc04-news.ops.worldnet.att.net>
 <1kzktalo9krea$.z8n9wev45xct$.dlg@40tude.net>
 <z9Dsg.2740$tE5.2374@news-server.bigpond.net.au>
Subject: Re: Ada vs Fortran for scientific applications
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <pPHsg.46977$VE1.46332@newssvr14.news.prodigy.com>
NNTP-Posting-Host: 70.134.98.164
X-Complaints-To: abuse@prodigy.net
X-Trace: newssvr14.news.prodigy.com 1152600405 ST000 70.134.98.164 (Tue,
 11 Jul 2006 02:46:45 EDT)
NNTP-Posting-Date: Tue, 11 Jul 2006 02:46:45 EDT
Organization: SBC http://yahoo.sbc.com
X-UserInfo1: 
 TSU[@I_AOHV[RVT[AROR__TDFZ\@@FXLM@TDOCQDJ@_@FNXACNVOPCWZBL[\YUWHANGYZEFNHFZPNLOBUNSS^_LGEVWEY\PHO@YJSSWBBDT\PFD^ESBTXVCCMTD]JCJLE\_IJMFNRY]SWE[S[D_CNB__ZK^VGVCKHA[S@COB^[@ZQSDFQ\BPMS@DZVUKQTJL
Date: Tue, 11 Jul 2006 06:46:45 GMT
Xref: g2news2.google.com comp.lang.ada:5604 comp.lang.fortran:11924
 comp.lang.pl1:1974
Date: 2006-07-11T06:46:45+00:00
List-Id: <comp.lang.ada>


"robin" <robin_v@bigpond.com> wrote in message 
news:z9Dsg.2740$tE5.2374@news-server.bigpond.net.au...
>
> Compilers can check for uninitialized variables during compilation.
>
True.  In fact, Ada compilers issue a warning for any variable
that is used before a value is assigned to it.    If a parameter is
included in a method (function/procedure/subroutine) and never
referenced, a warning is issued.    Sometimes the pragma
Normalize_Scalars is useful.   Often, the correct design is to
leave variables uninitialized until they are used so an exception
can be raised.   However, since the compiler will emit a warning
about variables that have never been assigned a value in an algorithm
that tries to use it, no harm is really done since the careful programmer
will not release a program with warnings in it.

So, I am assuming, Robin, that PL/I does something similar:  a warning
for any variable that is used in a program before a value is assigned to it.

Richard Riehle