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,147f221051e5a63d
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!postnews.google.com!d77g2000hsb.googlegroups.com!not-for-mail
From: Matthew Heaney <mheaney@on2.com>
Newsgroups: comp.lang.ada
Subject: Re: memory management in Ada: tedious without GC?
Date: Mon, 19 May 2008 16:02:43 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <63e1833a-ae58-4fd2-9268-e9779d820c39@d77g2000hsb.googlegroups.com>
References: 
 <4ddef8bf-b5b1-4d7e-b75b-386cd6c8402c@l17g2000pri.googlegroups.com>
	<482E8A9D.5040401@obry.net>
 <8640a12f-da99-435f-8eb6-372e175cd5b9@z72g2000hsb.googlegroups.com>
	<482F19CE.7060306@obry.net> <87d4nkzhtn.fsf@willow.rfc1149.net>
	<2545491.n7xu0MFufK@linux1.krischik.com>
 <ef669aad-89dd-4ac2-8911-ba4687c6dd6a@u6g2000prc.googlegroups.com>
	<5209773.UsCT0IWhbo@linux1.krischik.com>
 <82e2924a-4888-4b45-a4de-f33f905334c2@n1g2000prb.googlegroups.com>
	<155a4acc-8898-4316-88df-0b161bdadd9a@c58g2000hsc.googlegroups.com>
	<5f570e87-fd87-48cb-b991-a76c30648e79@y38g2000hsy.googlegroups.com>
	<b0bb8ae7-881b-4605-b20c-faa3a2f88a91@j22g2000hsf.googlegroups.com>
	<8d288545-e0c6-4f70-b3d5-3d037ab0bff2@y21g2000hsf.googlegroups.com>
NNTP-Posting-Host: 66.162.65.129
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1211238164 16739 127.0.0.1 (19 May 2008 23:02:44
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 19 May 2008 23:02:44 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: d77g2000hsb.googlegroups.com; posting-host=66.162.65.129;
	posting-account=umyUbgkAAADe5rQC4VzV-ffCoH4N30u3
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.14)
	Gecko/20080404 Firefox/2.0.0.14,gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:262
Date: 2008-05-19T16:02:43-07:00
List-Id: <comp.lang.ada>

On May 19, 5:21 pm, Maciej Sobczak <see.my.homep...@gmail.com> wrote:
>
> Note also that it prevents some obvious optimizations like avoiding
> memory allocator round-trip when for example short container is
> assigned to a longer one, which already has enough place for RHS.

Right.  I suppose if a strong guarantee is necessary, then you could
make the type limited and then provide an Assign operation.


> The memory is lost.
> OK, it is still managed by the relevant storage pool - but if the pool
> itself is not dynamically scoped (or the scope is just too wide), then
> it is effectively a leak.

I guess in that case you could use an indefinite type (limited or non-
limited -- it doesn't matter anymore in Ada05) and allocate the object
on the stack.

declare
  O : T := Initialize (...);
begin

In the event of an exception during initialization, the stack would
get unwound in the normal way and there would be no memory leak.

Cheers,
Matt