New boost::function allocator semantics?
What is the procedure for updating the boost::function allocator semantics according to http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2308.html? A working implementation is available here: http://www.revergestudios.com/boost-function/ I'm asking because it will break legacy code that uses the current allocator support in boost::function. Such legacy code would be very easy to fix (of course, legacy code that uses boost::function without supplying custom allocator will not break.) -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
On Mar 5, 2008, at 9:21 PM, Emil Dotchevski wrote:
What is the procedure for updating the boost::function allocator semantics according to http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2308.html?
A working implementation is available here: http://www.revergestudios.com/boost-function/
I'm asking because it will break legacy code that uses the current allocator support in boost::function. Such legacy code would be very easy to fix (of course, legacy code that uses boost::function without supplying custom allocator will not break.)
I've put this into the Subversion trunk. Since this is a non-trivial change, I wouldn't be surprised if there's a little churn while we figure out workarounds for the more broken platforms. Thanks to Emil for both the idea and the implementation. - Doug
participants (2)
-
Doug Gregor -
Emil Dotchevski