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,ed6a891101ff4e06
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: Freeing Pointers to classwide types
Date: 1998/10/09
Message-ID: <m3n277vsx2.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 399187825
Sender: matt@mheaney.ni.net
References: <1ftmFTC69GA.191@samson.airnet.net>
 <360b26a1.41575272@SantaClara01.news.InterNex.Net>
NNTP-Posting-Date: Thu, 08 Oct 1998 17:50:14 PDT
Newsgroups: comp.lang.ada
Date: 1998-10-09T00:00:00+00:00
List-Id: <comp.lang.ada>

tmoran@bix.com (Tom Moran) writes:

> >freeing the memory once you allocate it
> Look up Unchecked_Deallocation in your Ada text if you are worried
> about manually freeing memory, class-wide or not.

Please don't use Unchecked_Deallocation.  You must take responsibility
for storage management, otherwise you're at the mercy of your compiler
vendor.

(As time goes on, how does repeated use of new/dealloc affect
the heap?  What is the timing behavior?  I worked on a system that made
unbridled use of new/dealloc, and after a while calling allocator new
NEVER RETURNED TO THE CALLER.)

It's very simple to implement your own storage manager.