Boost logo

Boost :

From: Fernando Cacciola (fcacciola_at_[hidden])
Date: 2002-08-30 10:26:41

----- Original Message -----
From: "Carlo Wood" <carlo_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, August 30, 2002 11:34 AM
Subject: Re: [boost] Re: [Libcwd-devel] libcwd and Boost

> On Fri, Aug 30, 2002 at 10:01:12AM -0400, Rob Stewart wrote:
> > I still don't see the point. The library code can allocate and
> > deallocate memory as it sees fit. It can use new/delete,
> > std::allocator<...>, or whatever. As long as the library doesn't
> > allocate memory and hand it off to the caller, or if the memory
> > allocation is managed in an object that defers to the library to
> > release it, there is no problem.
> The reason I need this is because I have written a debugging
> library that needs to be able to do demangling from within malloc().
I see. Just out of curiosity: what is it that you need to demangle from
within malloc()? I though that demangling applied only to C++ type names
(and malloc is a C function).

Fernando Cacciola
Sierra s.r.l.

Boost list run by bdawes at, gregod at, cpdaniel at, john at