<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0"><font size="2"><span style="font-size:11pt;">Hi.<br>
</span></font></p>
<p style="margin-top:0;margin-bottom:0"><font size="2"><span style="font-size:11pt;">Christian wrote:</span></font></p>
<p style="margin-top:0;margin-bottom:0"><font size="2"><span style="font-size:11pt;"><br>
</span></font></p>
<p style="margin-top:0;margin-bottom:0"><font size="2"><span style="font-size:11pt;">> The modularisation is not about warnings. It goes mainly along concepts or interfaces.<br>
</span></font><br>
</p>
<p style="margin-top:0;margin-bottom:0">But with that combining localfunctions and geometry would be reasonable - both concern interfaces related to the reference element.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">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.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">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</p>
<p style="margin-top:0;margin-bottom:0">Andreas<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dune-devel <dune-devel-bounces@lists.dune-project.org> on behalf of Christian Engwer <christian.engwer@uni-muenster.de><br>
<b>Sent:</b> 13 June 2019 17:16:07<br>
<b>To:</b> dune-devel@lists.dune-project.org; Christoph Grüninger<br>
<b>Subject:</b> Re: [Dune-devel] Reduce number of core modules?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Christoph,<br>
<br>
I believe there is a major misunderstanding between the two of you regarding the modularisation.<br>
<br>
>Because it would oppose the modularity as I see it. I don't want to<br>
>built UGGrid and get all its warnings, if I don't want to use it. <br>
<br>
The modularisation is not about warnings. It goes mainly along concepts or interfaces.<br>
<br>
>This<br>
>is not the case for geometry or ISTL, most of the disretization<br>
>packages<br>
>use them anyway.<br>
><br>
>I would like to hear more opinions.<br>
<br>
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.<br>
<br>
Ciao<br>
Christian<br>
<br>
_______________________________________________<br>
Dune-devel mailing list<br>
Dune-devel@lists.dune-project.org<br>
<a href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a></div>
</span></font></div>
</body>
</html>