E. Gladyshev wrote:
> --- Peter Dimov <[EMAIL PROTECTED]> wrote:
>
>> unless there are very solid reasons for the allocator parameter. ;-)
>
> I agree, but the problme is that I don't know whether I have a solid
reason or not.
> I have to ship my class to someone else. She might have a solid reason, I
don't know.
> If I supply an allocator parameter, then I am covered and I can sleep
well. :)

Well... if you ask me, it is better to not offer the functionality until
someone explicitly asks for it and gives a reasonable scenario as an
example. Features are easy to add, hard to remove, and there is always the
possibility that you "pre-included" the wrong feature.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to