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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cca!mirror!ishmael!ada-uts!stt
From: stt@ada-uts
Newsgroups: comp.lang.ada
Subject: Named block inside named loop
Message-ID: <57900049@ada-uts>
Date: Fri, 23-Oct-87 12:18:00 EST
Article-I.D.: ada-uts.57900049
Posted: Fri Oct 23 12:18:00 1987
Date-Received: Wed, 28-Oct-87 01:27:54 EST
Nf-ID: #N:ada-uts:57900049:000:800
Nf-From: ada-uts!stt    Oct 23 11:18:00 1987
List-Id: <comp.lang.ada>


In response to the question about declaring
a named block inside a named loop ...
LRM 5.1:3 says:
   A label name, and similarly a loop or block name, is implicitly
declared at the end of the declarative part of the innermost block
statement, subprogram body, package body, task body, or generic
body that encloses the labeled statement, the named loop statement,
or the named block statement, as the case may be.

This means that when you have:

   procedure xyz is
   begin
      loop_name : loop
          block_name : declare
              X : integer;
          begin
	      . . .
	      
that the "full name" for X is standard.xyz.block_name.X.

Only the loop index, if any, is considered to be declared
as a local of the loop statement.

S. Tucker Taft
Intermetrics, Inc.
Cambridge, MA  02138