Re: [Boost-users] How to manage the internal memory allocation in boost libraries?

Subject: Re: [Boost-users] How to manage the internal memory allocation in boost libraries?
From: Tang Jiang Jun (tangjiangjun_at_[hidden])
Date: 2010-09-10 10:21:41

Such as any, asio, etc.

But redefining global new operator is dangerous, and prone to conflict with
global static objects which use the memory heap before custom memory heap
manager get initialization.

Actually why do most of boost libraries not provide the allocator interface
to help users to manage their memory, as the way STL offers?

On Fri, Sep 10, 2010 at 1:05 PM, Mathias Gaunard <
mathias.gaunard_at_[hidden]> wrote:

> On 10/09/2010 10:04, Tang Jiang Jun wrote:
>
>> Hello,
>>
>> I am seeking a way to manage the internal memory allocation in boost
>> libraries, and it seems that most of boost libraries do not support
>> allocator parameter, so they can not be handled like STL library.
>>
>
> What libraries are you thinking of?
>
>
>
>  But for my project, our memory management need to control all the memory
>> allocation even it happens in the third-party libraries.
>> Could somebody give me some suggestions to accomplish that?
>>
>
> You could redefine operator new.
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>