[Dune-devel] Reduce number of core modules?

[Dedner, Andreas]

Hi.

Christian wrote:


> The modularisation is not about warnings. It goes mainly along concepts or interfaces.


But with that combining localfunctions and geometry would be reasonable - both concern interfaces related to the reference element.


The case for istl and common and not quite so strong although they do both have a lot of 'linear algebra' related interfaces in common.


The is therefore a case for reducing the 5 core modules to 3  to be made without breaking that concept of modularity. I haven't really made up my mind

Andreas

________________________________
From: Dune-devel <dune-devel-bounces at lists.dune-project.org> on behalf of Christian Engwer <christian.engwer at uni-muenster.de>
Sent: 13 June 2019 17:16:07
To: dune-devel at lists.dune-project.org; Christoph Grüninger
Subject: Re: [Dune-devel] Reduce number of core modules?

Hi Christoph,

I believe there is a major misunderstanding between the two of you regarding the modularisation.

>Because it would oppose the modularity as I see it. I don't want to
>built UGGrid and get all its warnings, if I don't want to use it.

The modularisation is not about warnings. It goes mainly along concepts or interfaces.

>This
>is not the case for geometry or ISTL, most of the disretization
>packages
>use them anyway.
>
>I would like to hear more opinions.

I think meeting the grid-howto into dune-grid will help maintainence, I would also like to see uggrid directly available with dune-grid, but this is a different story. I don't see any good reason to merge ISTL into common, or geometry or localfunctions.

Ciao
Christian

_______________________________________________
Dune-devel mailing list
Dune-devel at lists.dune-project.org
https://lists.dune-project.org/mailman/listinfo/dune-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20190613/06f5a9c7/attachment.htm>