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!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 11 Jul 2006 17:44:23 -0500
Date: Tue, 11 Jul 2006 15:44:55 -0700
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada,comp.lang.fortran,comp.lang.pl1
Subject: Re: Ada vs Fortran for scientific applications
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>
 <pPHsg.46977$VE1.46332@newssvr14.news.prodigy.com> <kROsg.7$Pg1.2@fe11.lga>
 <eul09e.bgk.ln@hunter.axlog.fr>
In-Reply-To: <eul09e.bgk.ln@hunter.axlog.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <R4-dncJT3YFatCnZnZ2dnUVZ_oKdnZ2d@comcast.com>
NNTP-Posting-Host: 24.18.174.4
X-Trace: 
 sv3-oZzHTNJf41NwIPQ0r0p34R6zrTZMaxATIe/F55FvOsSQbiBGUglH2+vu+90JG27H6y54tU3ubLKDtlP!Hw1/2yuw50ZRtFfqzsRm22NtbF+WzIJhViK6WyAopwfvUji50xar08zvG0bBXgqf4+ksAePSEU3H!QgKpIg==
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news2.google.com comp.lang.ada:5629 comp.lang.fortran:11960
 comp.lang.pl1:1996
Date: 2006-07-11T15:44:55-07:00
List-Id: <comp.lang.ada>

Jean-Pierre Rosen wrote:
(snip)

> But it doesn't work! In Java, you have the rule that every variable must 
> be initialized before being used, PLUS the rule that every variable is 
> initialized automatically to zero! Why that? Because with a clever use 
> of initializers, you can still access variables before they are 
> initialized...

It might be that arrays are initialized to zero when created,
but that is more like C's malloc().  (Well, calloc() I suppose.)
Automatic variables, which are scalars, are not initialized
to zero automatically.

Only scalar variables are checked for initialization, but then
an array is really an initialized object reference variable.
If that variable isn't properly initialized, compilation will fail.

-- glen