Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!ai-lab!rice-chex!rpk
From: rpk@rice-chex.ai.mit.edu (Robert Krajewski)
Newsgroups: comp.lang.c++
Subject: Heapness {was: testing 'this'}
Message-ID: <11376@life.ai.mit.edu>
Date: 15 Oct 90 20:30:37 GMT
References: <1990Oct14.224706.1934@nowhere.uucp> <12148@cadillac.CAD.MCC.COM>
Sender: news@ai.mit.edu
Organization: MIT Artificial Intelligence Laboratory
Lines: 20

Actually, I've needed to know something more specific, and thus the
question is more manageable: can this object be >delete<ed later ?
(This is need to implement a facility where objects can be deleted/
destructed if something abnormal happens during their use, inside a
context with a short lifetime.)

The way this is done: I need a table for the objects I'm managing
anyway, so I overload new in the base class of object that live in the
table to enter the object in the table.  The base class constructor
runs after new, so I know that new ran if the constructor already
finds the object in the table.

Now, this assumes that the constructor is run after the corresponding
class to that operator new (but note that I used a table, so it
doesn't have to be immediately after), which I guess is a pretty
reasonable assumption.

----
Robert P. Krajewski
Internet: rpk@ai.mit.edu ; Lotus: robert_krajewski.lotus@crd.dnet.lotus.com