dynamic_bitset constructor problem

[rick68@…]

Two constiructors in dynamic_bitset:

============================================ dynamic_bitset(size_type num_bits, unsigned long value = 0, const Allocator& alloc = Allocator())

and

template <typename BlockInputIterator> dynamic_bitset(BlockInputIterator first, BlockInputIterator last, const Allocator& alloc = Allocator()) ============================================

If I want to create dynamic_bitset object with 8 bits and default value 0x07 ("dynamic_bitset(8, 0x07)"), that will use second constructor, not first.

[Gennaro Prota]

Yep. The match is normal; but the second constructor should detect the case and "do the right thing", as standard sequences are required to do (though, of course, dynamic_bitset isn't such a beast).

I had implemented this, but didn't commit it because, back then, I didn't have enough time to follow the regression reports, and the code has (by experience) a fair potential to break on several broken compilers and libraries (yeah... broken on broken :-)). I'll do it now, as soon as I'll see the result of some other changes I applied this morning. BTW, I only saw your report today.

Thanks,
Gennaro.

[Gennaro Prota]

It's now committed, both on trunk and branches/release, so it will be in Boost 1.37.0. The updated documentation can be browsed at

• trunk/libs/dynamic_bitset/dynamic_bitset.html
  

or

• branches/release/libs/dynamic_bitset/dynamic_bitset.html