Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: realloc equivalent in C++
Message-ID: <6590130@hplsla.HP.COM>
Date: 22 May 89 16:58:46 GMT
References: <80@citycs.UUCP>
Organization: HP Lake Stevens, WA
Lines: 12

Good question.  I suspect the answer, in part, is going
to lie in the implementation of a particular C++ compiler's
implementation of new and delete -- which I haven't yet
seen documented on any compilers.  Why not just continue
to use malloc/realloc?  If you just need a chunk of memory
you should be able to continue to use these as always.

If you actually need this feature for object creation and
destruction, then presumably you need the capability
rumored for future release in C++ compilers -- the ability
to take over allocation/deallocation for a particular class
by overloading new/delete.