From: Amit (contact.lipik_at_[hidden])
Date: 2008-04-03 07:40:33
Joaquin M Lopez Munoz <joaquin <at> tid.es> writes:
> Steven is right on spot: boost::fast_pool_allocator is not correctly
> specialized for void, as it should. I'll file a bug report about this.
> In the meantime, you can simply replace fast_pool_allocator with
> the following fixed_fast_pool_allocator class:
Many thanks. Your specialization makes the code compile OK - have to make other
changes (for new thread interface) before I can run it, will report on the
I think whole of pool needs a review - I think it hasn't been updated for a
while. Maybe I'll volunteer once I have shipped my current project :)
By the way, the release notes for 1.35 state that equal_range is now more
efficient - are we talking better computational complexity here, or less
overhead? Could you please point me to a description of the changes so I know
what sort of improvement should be expected. And does this mean that the
predicate based range lookup functions exposed by multi-index (ones that take a
lower & uper bounder) are more efficient as well?
Thanks again. Multiindex is an amazingly useful library.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk