From: Emil Dotchevski (emil_at_[hidden])
Date: 2007-11-01 17:38:00
> Would this not break all code currently using the templated allocator
> version of boost::function? I would call that not at all appropriate for a
> dot release, and should be avoided outright if possible.
I apologize I meant 1.35 but now I see that it was naive to think it
could happen that soon. My understanding is that Doug himself wanted
the new allocator semantics for boost::function merged into Boost, but
perhaps we should have a discussion first.
About breaking user code -- yes, it's a breaking change but I think
that most people will not be affected, because using allocators with
boost::function is not very practical with the legacy allocator
semantics, and switching to the new allocator semantics is trivial.
It is also possible to introduce a macro that switches the legacy
allocator semantics on (the allocator change affects only 2 hpp
-- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk