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,42a57c8ee023f14d
X-Google-Attributes: gid103376,public
From: Hannes Haug <Hannes.Haug@Student.Uni-Tuebingen.de>
Subject: Re: Q: memory management
Date: 1996/06/19
Message-ID: <uvvrarccfu4.fsf@chaq.informatik.uni-tuebingen.de>#1/1
X-Deja-AN: 160991118
sender: haugha@chaq.informatik.uni-tuebingen.de
references: <uvvg27t9v68.fsf@chaq.informatik.uni-tuebingen.de>
organization: Uni Tuebingen
newsgroups: comp.lang.ada
Date: 1996-06-19T00:00:00+00:00
List-Id: <comp.lang.ada>


>>>>> "TT" == Tucker Taft <stt@henning.camb.inmet.com> writes:

    TT> Solution: You implement your own storage pool.  Which probably
    TT> ends up calling "malloc" or some even lower level operation.
    TT> That's what happens when you start getting too theoretical
    TT> ;-).

But some mallocs suck. Some are thread save others not. Perhaps there
even isn't a malloc available. A lot of problems if I'm too theoretical ;-)

 - hannes