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,FREEMAIL_FROM
	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!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!inka.de!rz.uni-karlsruhe.de!news.rz.uni-karlsruhe.de!not-for-mail
From: Florian Liekweg <liekweg@gmx.de>
Newsgroups: comp.lang.ada
Subject: Re: Heap Memory Management Question(s)
Date: Wed, 05 Apr 2006 12:51:34 +0200
Organization: University of Karlsruhe, Germany
Message-ID: <4433A136.6080503@gmx.de>
References: <443242EC.2060603@gmx.de> <wccu099s7ma.fsf@shell01.TheWorld.com>
NNTP-Posting-Host: i44dyn35.info.uni-karlsruhe.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news2.rz.uni-karlsruhe.de 1144234295 25203 172.22.85.227 (5 Apr 2006
 10:51:35 GMT)
X-Complaints-To: usenet@rz.uni-karlsruhe.de
NNTP-Posting-Date: Wed, 5 Apr 2006 10:51:35 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
 rv:1.7.12) Gecko/20060305
X-Accept-Language: en-us, en
In-Reply-To: <wccu099s7ma.fsf@shell01.TheWorld.com>
Xref: g2news1.google.com comp.lang.ada:3727
Date: 2006-04-05T12:51:34+02:00
List-Id: <comp.lang.ada>

Robert A Duff wrote:
> You might want to take a look at the (draft) Ada 2005 manual,
> which is available somewhere on www.adaic.com.
> 
> Also, John Barnes' book has a nice discussion of access types and
> storage pools and whatnot.
Thank you for the pointers!

> I removed the term "collection" from the Ada 95 RM, because [reason]
> [...]
> [...]  I don't think it's a good idea,
> especially now that we have storage pools.  In my experience,
> approximately zero access types are nested inside procedures
> anyway.
That's what I wanted to know, but I fear I have introduced a
misunderstanding here:

> I'm not sure what you mean by "left momentarily", [...]

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.

> [...] hundreds of reasonable
> ways of managing heap memory, none of which is best for all purposes.
> [...]  storage pools [...]
Yes, indeed.  I am keeping an eye on Ada, because it seems to me
that it takes this subject more seriously than, e.g. C++ and friends,
and is not afraid to unload some of the work associated with it onto
the compiler.

-- Florian