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,109419a9e4966aaf
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!t31g2000cwb.googlegroups.com!not-for-mail
From: "jimmaureenrogers@worldnet.att.net" <jimmaureenrogers@worldnet.att.net>
Newsgroups: comp.lang.ada
Subject: Re: Heap Memory Management Question(s)
Date: 5 Apr 2006 09:50:50 -0700
Organization: http://groups.google.com
Message-ID: <1144255845.663485.207140@t31g2000cwb.googlegroups.com>
References: <443242EC.2060603@gmx.de><wccu099s7ma.fsf@shell01.TheWorld.com>
   <4433A136.6080503@gmx.de>
NNTP-Posting-Host: 209.194.156.4
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1144255855 27624 127.0.0.1 (5 Apr 2006 16:50:55
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 5 Apr 2006 16:50:55 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0;
 Windows NT 5.0),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: t31g2000cwb.googlegroups.com; posting-host=209.194.156.4;
   posting-account=SqOfxAwAAAAkL81YAPGH1JdBwpUXw9ZG
Xref: g2news1.google.com comp.lang.ada:3729
Date: 2006-04-05T09:50:50-07:00
List-Id: <comp.lang.ada>

Florian Liekweg wrote:
> Sorry for being unclear.  I was thinking of, e.g., a package variable,
> which, as I understand, is not visible and/or accessible everywhere,
> but it exists and keeps its state over the lifetime of the program.
>
> My assumption is the following:
>    We can momentarily leave the area where the variable is /visible/,
>    but it stays in existence.  The lifetime of the object it points to
>    can now span the entire program, not just the time the variable is
>    visible.
> My conclusion is: Visibility of the access type doesn't help when it
>    comes to determining the lifetime of that object.  NB, it could
>    of course /improve/ whatever analysis a sophisticated compiler
>    might do.

You might want to read the "Ada Distilled" article by Richard Riehle.
It is available several places online.

Ada Distilled has a good discussion of how Ada makes a distinction
between scope and visibility. Richard argues that understanding this
distinction is critical to understanding Ada.

Another point to understand about Ada is that the language
design reduces the need to use access types compared to Java,
C++, or C#.

Jim Rogers