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-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c840deaa6965e67a
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-01-27 22:49:53 PST
Newsgroups: comp.lang.ada
Path: 
 nntp.gmd.de!news.rwth-aachen.de!uni-paderborn.de!news.sni.de!aquila.sni-usa.com!noc.near.net!cambridge-news.cygnus.com!bloom-beacon.mit.edu!Shiva.COM!world!bobduff
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Memory overwrite?
Message-ID: <D32HMF.FM9@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
References: <3g86nm$mj3@miranda.gmrc.gecm.com>
Date: Fri, 27 Jan 1995 14:01:26 GMT
Date: 1995-01-27T14:01:26+00:00
List-Id: <comp.lang.ada>

In article <3g86nm$mj3@miranda.gmrc.gecm.com>,
R.A.L Williams <bill@valiant> wrote:
>procedure CRASH is
>  subtype CONSTRAINED_INT is INTEGER range 2 .. 5;
>  I : INTEGER;
>  J : CONSTRAINED_INT;
>  X : array(CONSTRAINED_INT) of INTEGER;
>begin
>  for I in CONSTRAINED_INT'RANGE loop

GNAT also ought to warn that this I is different from the one declared
above, since the for loop automatically declares a new I!  ;-)

- Bob