[Dune] Returning Geometries As Objects

[Markus Blatt]

On Wed, Jan 25, 2012 at 11:04:36AM +0100, Jö Fahlke wrote:
> Am Wed, 25. Jan 2012, 09:49:01 +0100 schrieb Martin Nolte:
> > The changes try to be as uninvasive as possible. However, due to
> > code evolution, there are some unnecessary changes left. The
> > greatest benefit for a developer is the possibility to create a new
> > geometry object whenever the geometry is requested. This gives us
> > essentially two types of geometry implementations:
> > (a) actually returned geometry implementations,
> > (b) references to the actual geometry (as was previously enforced).
> 
> So, in essence, Dune::Geometry may (a) store the actual geometry or may (b) be
> a wrapper class holding a reference/pointer to the actual geometry?
> 
> In case be (b), how long is a geometry object guaranteed to be valid?  Until
> the entity/intersection object it was obtained from changes it's value or is
> destroyed?
>

Who chooses between a and b? Does the user of the grid have the choice
or does the grid developer decide whether a or b is available?

Kind regards,

Markus

-- 
Do you need more support with DUNE or HPC in general? 

Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
Rappoltsweilerstr. 5, 68229 Mannheim, Germany
Tel.: +49 (0) 160 97590858  Fax: +49 (0)322 1108991658