Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!telesoft!rlk
From: rlk@telesoft.com (Bob Kitzberger @sation)
Newsgroups: comp.realtime
Subject: Re: Memory management under VxWorks
Keywords: VxWorks, memory fragmentation, programmer frustration
Message-ID: <713@telesoft.com>
Date: 25 Feb 90 00:35:40 GMT
References: <8136@pt.cs.cmu.edu>
Organization: TeleSoft, San Diego, CA.
Lines: 22

In article <8136@pt.cs.cmu.edu>, hmp@cive.ri.cmu.edu (Henning Pangels) writes:
> 
> An approach I've thought about is to create the objects you need when you
> need them, and reuse them from then on whenever possible. In a way, that
> amounts to writing you own memory manager, which is something an application
> really shouldn't have to deal with. 

This is the rationale behind Ada's "sized collections".  When
specifying an access type (pointer), you can pre-allocate a storage
area in a global heap to use for all dynamic allocations of that type.
Prevents framentation yet allows flexibility in dynamic data
structures.  Provisions are provided to prevent garbage collection on a
collection-by-collection basis.

	.Bob.

-- 
Bob Kitzberger                  Internet : rlk@telesoft.com
TeleSoft                        uucp  :    ...!ucsd.ucsd.edu!telesoft!rlk
5959 Cornerstone Ct. West       at&t  :    (619) 457-2700 x163
San Diego, CA 92121-9891        "Dawn : The time when men of reason go to bed."
------------------------------------------------------------------------------