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-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,29850945228df59
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-21 12:04:36 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!feed.news.nacamar.de!news.belwue.de!news.uni-stuttgart.de!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: Boehm-Demers-Weiser conservative garbage collector and GNAT
Date: Sat, 21 Jun 2003 21:04:30 +0200
Message-ID: <874r2js14x.fsf@deneb.enyo.de>
References: <1316747.mXveBPtf0Z@linux1.krischik.com>
 <rw2wufl6po1.fsf@lbrenta.corp.emc.com>
 <slrnbetosb.8i1.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <rw2of0x6m6j.fsf@lbrenta.corp.emc.com>
 <slrnbetrm0.atf.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <rw2k7bk7web.fsf@lbrenta.corp.emc.com>
 <slrnbeu1ht.big.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <Hazco47MvHdL@eisner.encompasserve.org>
 <slrnbeu47b.c8f.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <rw27k7k7rgo.fsf@lbrenta.corp.emc.com>
 <QdZxXhgRp7Ti@eisner.encompasserve.org>
 <rw2wufk67oa.fsf@lbrenta.corp.emc.com> <uhe6otzmj.fsf@nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: albireo.enyo.de 1056222270 3066 212.9.189.171 (21 Jun 2003 19:04:30
 GMT)
X-Complaints-To: 
Cancel-Lock: sha1:4uT0JDaTsROPjYL8C4j35MnvaXE=
Xref: archiver1.google.com comp.lang.ada:39531
Date: 2003-06-21T21:04:30+02:00
List-Id: <comp.lang.ada>

Stephen Leake <Stephe.Leake@nasa.gov> writes:

> I wrote a container library that does all the memory management I
> need.

How do you prevent client code from keeping references to objects in
the container at the point of its finalization?  Is erroneous
execution a possibility?

I don't think memory leaks are the most severe problem, dangling
references are.