[dune-pdelab] Patches

[Steffen Müthing]

> Am 23.04.2015 um 06:34 schrieb Oliver Sander <sander at igpm.rwth-aachen.de>:
> 
> Am 23.04.2015 um 00:38 schrieb Christian Engwer:
>> I suggest to create the appropriate 2.4 branch and then we can merge
>> the functions patches to master.
>> 
>> Is there a particular reason _not to branch_ at the end of the week?
> 
> Not from my side.

I have no idea about the current state of PDELab (and the Howto) - there are a lot of patches
to get rid of deprecation warnings, but there are also some subtle issues with lifetimes of the
temporaries returned from inside() / outside() that I need to take a look at. But right now I’m pretty
occupied with the EXADUNE poster, so I don’t think any branching before the end of next week
isn’t realistic.

Steffen

PS: Basically, you really don’t want anything like ig.inside().type() dotted around in your code -
capture the outside cell in a temporary once, and then use that. The subtle issue come into play
in some of the grid loops, but I’ll have to take a closer look at those. Marian has a similar set of
patches for the local operators as the one that was already applied by Christian, but it’s more
comprehensive. I’ll probably apply those on top (they also clean up the handling of the quadrature
loop and introduce the temporaries for the cells).

> --
> Oliver
> 
>> 
>> Christian
>> 
>> On Fri, Apr 17, 2015 at 09:27:31PM +0200, Christian Engwer wrote:
>>> Hi Steffen,
>>> 
>>>> do you really want to stay compatible with ALUGrid 1.52 for the next PDELab
>>>> release? I think we should just tell people to install the new dune-alugrid module
>>>> and be done with it…
>>> 
>>> it is not only alugrid. If we want to offer users a safe upgrade path,
>>> it would be good, if old grids work with the new interface. I have a
>>> branch (I'm going to push it later tonight) with basically adds the
>>> entity methods to the entitypointer and forwards them. By this it is
>>> possible to use the a non-ported grid.
>>> 
>>>> Oh, by the way: I would suggest calling the next PDELab release 2.4. It looks
>>>> like we are moving to a release schedule that is in sync with the core modules,
>>>> and by having the same release numbers it becomes a lot easier for people to
>>>> pick the correct version of PDELab.
>>> 
>>> Yes, we should call it 2.4.
>>> 
>>> Ciao
>>> Christian
>>> 
>>> _______________________________________________
>>> dune-pdelab mailing list
>>> dune-pdelab at dune-project.org
>>> http://lists.dune-project.org/mailman/listinfo/dune-pdelab
>> 
> 
> 
> _______________________________________________
> dune-pdelab mailing list
> dune-pdelab at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-pdelab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune-pdelab/attachments/20150423/ffbd6338/attachment.sig>