#453 Dune::BlockBitField is not a replacement for std::vector<Dune::BitField>
|Reported by||Christian Engwer (firstname.lastname@example.org)|
|Reported at||Nov 5, 2008 17:20|
|Version||Git (pre2.4) [autotools]|
|Operating System||Unspecified / All|
|Last edited by||Christian Engwer (email@example.com)|
|Last edited at||Nov 14, 2008 17:47|
|Closed by||Christian Engwer (firstname.lastname@example.org)|
|Closed at||Nov 14, 2008 17:47|
|Closed in version||Unknown|
The are several problems when using Dune::BlockBitField instead of std::vectorDune::BitField:
- several container interface typedefs of Dune::BlockBitField are wrong.
- Dune::BlockBitField inherits the iterators from std::vector, which does something completely different compeared to std::vectorDune::BitField::iterator
- The references returned by operator do not provide the full Dune::BitField interface, especially the nSetBits operation is missing.
I tried to change my application to use Dune::BlockBitField instead of Dune::BitField, but failed totally up to now. During these attempts I started fixing some the mentioned problems, but atm it is to much to fix everything.