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

Dune dune at dune-project.org
Sat Dec 5 17:32:29 CET 2009


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)

----------
Let me clarify my problem with solution (c). For "normal" dune grids (i.e., dune grids that don't wrap other dune grids), the solution looks perfect. Once you have to wrap another dune-grid, you get the following problem:
* implement an entity pointer wrapping the host entity pointer
* implement the iterator by deriving from the (wrapped) entity pointer.
The entity pointer already stores the host entity pointer. Now, you have to store the host iterator inside your iterator wrapper. Hence, the iterator wrapper stores the host entity pointer twice: Once in the entity pointer base class and a second time in the host iterator inside the iterator wrapper.

You might get a better understanding of what I'm talking about by looking into the GeometryGrid's entity pointer / iterator.

In my opinion, any solution to this problem should also solve the problem of meta-grids (like GeometryGrid). The reason is that we claim DUNE to be a negligible layer around any grid implementation, unifying the API. Hence, if DUNE is not able to wrap a DUNE grid with negligible effort, my opinion would be that we fail in this (important) design goal.

----------

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

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