... People are adopted to follow similar requirements for STL allocators anyway.
I guess they can be recommended to all boost authors who wants to make memory management data types.
Perhaps they can be added to the "Guidlines" section http://www.boost.org/more/lib_guide.htm#Guidelines
At the least, we could add the following bullet
* Discussion of memory management strategy.
to http://www.boost.org/more/lib_guide.htm#Documentation
I'm reluctant to say very much more at this point, as my opinions may not be suited to the needs of the many different libraries in Boost. But I think it's generally reasonable to: * not allocate memory unless it's really necessary * use the standard mechanisms (::operator new or std::allocator) when it is necessary * use custom allocation mechanisms only when there is a clear advantage to doing so * parameterize only when there is a clear advantage to doing so * use the standard parameterization mechanisms (Allocator) when choosing to parameterize * use custom parameterization mechanisms only when there is a clear advantage to doing so * document whether and how a library allocates memory
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
