[dune-pdelab] PDELab release

Steffen Müthing steffen.muething at iwr.uni-heidelberg.de
Tue May 5 15:06:50 CEST 2015


Hi everyone,

with the core modules branched, we should start thinking about the release of PDELab 2.4.

Before we can branch off the release, there are still some issues to discuss and decide:

1) What will be our minimum compiler requirements? I am *very much* opposed to anything
    below 4.6, as that gives us range-based for, clear semantics for move operations (I’ve had some
    nasty problems with autogenerated move member functions in 4.5) as well as constexpr.

    That said, my suggestion would be GCC 4.7, as that also gives us template aliases and delegated
    constructors. Moreover, I am unable to run decent testing for GCC < 4.7 on my machine because
    DUNE itself doesn’t support older GCC on OS X, so until we have some automatic testing infrastructure
    and a development model that makes it easy to use such an infrastructure (e.g. pull requests), I’ll probably
    break GCC 4.6 from time to time.

2) What’s our position regarding ALUGrid? My suggestion is to simply require the new dune-alugrid
     module and be done with it.

3) Somehow related to this: Christian already did some work on cleaning up the heaps of deprecation
    warnings due to the changed grid interface, but IMHO we should do a coordinated sweep of the
    complete code base PDELab and the Howto and also take the chance to improve coding style in
    general: range-based for loops (e.g. for quadrature loops), store inside and outside entities and
    geometries in variables for better performance etc.


What do you all think?

Steffen
-------------- 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/20150505/9ecf5c25/attachment.sig>


More information about the dune-pdelab mailing list