[Dune] [#674] strict-aliasing warnings with gcc-4.4

Dune flyspray at dune-project.org
Tue Dec 21 17:03:55 CET 2010


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#674 - strict-aliasing warnings with gcc-4.4
User who did this - Martin Nolte (nolte)

----------
>From my point of view, Iterators are a model of an entity pointer, i.e., they satisfy the same interface. The key difference from the previous presentation is, that an iterator and the normal entitypointer are two complete different objects (like std::vector and std::map, which are both containers).

The implication is: Whereever you need an entity pointer, you can also use an iterator. But you may not expect an object of type EntityPointer (unlike in dynamic polymorphism).

The new source of confusion might be naming: There is a concept EntityPointer and each grid also provides a type EntityPointer. These are two entirely different things. Each iterator remains a model of the EntityPointer concept, but it no longer associated with the type EntityPointer (as exported by the grid). In view of the upcoming release, we should maybe update the documentation to state this ambiguity explicitly.
----------

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

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.




More information about the Dune mailing list