[Dune] [#453] Dune::BlockBitField is not a replacement for std::vector<Dune::BitField>

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#453 - Dune::BlockBitField is not a replacement for std::vector<Dune::BitField>
User who did this - Carsten Gräser (Carsten)

----------
Sorry, I sent the above post befor I read your last posts. Regarding the interface:
If you want the standard interface you must be able to return real references. This requires that they point to some object which exists somewhere. But the bits only exist as part of a larger object and not as bool(=char). That's the reason why temp. objects of proxi(reference)-classes must be returned and it's also the reason why vector<bool> is neitehr a container not a sequence (see clause 23,24).
Besides that it's very nice to have the full BitSet interface. Thanks a lot for implementing it.
In my opinion it should be possible to also use the BlockBitFieldReference as bool for BlockBitField<1> to be able to replace the old BitField without the additional [0].
Renaming it to BlockBitSet would not be a good idea since the block-structure is already present in BitSet. BitSetVector would be more appropiate.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=453#comment628

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.