[boost] Re: Boost memory management guidelines

From: David Abrahams (dave_at_[hidden])
Date: 2003-09-02 12:41:09

"E. Gladyshev" <egladysh_at_[hidden]> writes:

> --- David Abrahams <dave_at_[hidden]> wrote:
> [...]
>> Just how do you propose to prevent people from writing their own
>> construct/destroy functions?  And if they write an allocator from
>> scratch, but *don't* provide construct/destroy manually, where will
>> they come from?
>
> What I meant is that if boost allocators won't include constuct/destroy,
> all boost developers will probably implement their own construct/destroy
> helper functions (outside allocators) to construct/destroy object using
> allocators.
> In such case, I suggested to include standard 
> construct/destroy functions 
> in boost (not in allocators).

Good idea.

You wrote:

> I think construct/destroy can be implemented as non-customizable 
> static functions in boost just for convinence.

I think the word "static" is not what you meant, and is what led me
to challenge the suggestion.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com