[Dune] [#604] move reference element related stuff to separate module
Dune
flyspray at dune-project.org
Mon Jun 13 13:19:40 CEST 2011
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#604 - move reference element related stuff to separate module
User who did this - Jö Fahlke (joe)
----------
Does anybody have a good idea how to move the GeometryType? All the other
stuff is relatively straight forward. My best approaches are:
1. Move everything GeometryType-related to Dune-Geometry and leave
compatibility headers with a deprecation warning in Dune-Common. These
headers include the real stuff from Dune-Geometry. This is ugly because
it means Dune-Common includes stuff from a module it can't depend upon.
2. Move everything GeometryType related to Dune-Geometry and have
compatibility headers <dune/common/geometrytype.hh> etc. *inside*
*Dune-Geometry*. This is ugly because it means that Dune-Geometry
infridges on Dune-Common's namespace. Also, to anybody who isn't
automatically using Dune-Geometry it will look like
<dune/common/geometrytype.hh> simply vanished without any real clue what
has been going on.
Since most users are likely to use Dune-Localfunctions or Dune-Grid,
dunecontrol will tell them they need Dune-Geometry, so everything should work
seamlessly for both approaches in the vast majority of cases.
----------
More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=604#comment2610
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