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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,530474eb5e6fefe1
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: using 'address to make indrect calls
Date: 1999/07/02
Message-ID: <wccso776ufq.fsf@world.std.com>#1/1
X-Deja-AN: 496413863
Sender: bobduff@world.std.com (Robert A Duff)
References: <3779194C.45EA@b.com> <wcck8skfstf.fsf@world.std.com>
 <dale-0107992249220001@192.168.0.2>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-07-02T00:00:00+00:00
List-Id: <comp.lang.ada>

dale@cs.rmit.edu.au (Dale Stanbrough) writes:

> Robert A Duff wrote:
> 
> " An up-level reference is when a procedure refers to an object declared
>   outside of that procedure."
> 
> 
> Is that the case even for package based variables/static in C?

Well, I'm not sure if that should be called an uplevel ref or not.
Probably not.  It's certainly not usually implemented the same way.
OTOH, you can view this as just an optimization of the bottom-most
stack frame of the environment task.

- Bob
-- 
Change robert to bob to get my real email address.  Sorry.