#63 Dune::Entity, Dune::Geometry (Engine vs. Barton-Nackman)
Metadata
| Property | Value |
|---|---|
| Reported by | Robert K (robertk@posteo.org) |
| Reported at | Dec 9, 2005 11:01 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Robert K (robertk@posteo.org) |
| Last edited at | Jan 16, 2006 17:34 |
| Closed by | Robert K (robertk@posteo.org) |
| Closed at | Feb 16, 2006 15:00 |
| Closed in version | 1.0 |
| Resolution | Implemented |
| Comment | The concept of choice is the engine concept for the classes Level-, Leaf-, Hierarchic-, IntersectionIterator and Entity and Geometry. The former Interface classes like GeometryInterface have been removed. Now the GridDefaultImplementation can access the realImplementation of the Interface Objects. The create such Interface Objects one can use the MakeableInterfaceObject class in grid.hh. |
Description
As Entities in Dune are only returned as references one could omit the Dune::Entity class and return a reference (for example in the dereference methods) to the interface class as already used for the index sets. This has the advantage that 2 classes could be removed (Dune::Entity, GridImp::MakeableEntity) and also hacks like the getRealEntity would not be necessary anymore. The usage outside (for the user) is exactly the same. This would clarify the grid interface more, because the implementer doesn't have to implement 2 entity classes and also there would exist only one entity interface class. The same applies for the Geometry classes. For the iterators one has to use the engine concept, because there are objects returned instead of references.