THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#214 - Implement naming rules for class names User who did this - Bernd Flemisch (bernd) ---------- Since we already talk about naming and structure, we should have a look here again. I want to evaluate whether we should introduce additional subnamespaces of the namespace "Dumux" (we already have "Properties" and "FluidSystem"). This would especially pay off for the implicit and decoupled models. Statt der Klasse/Datei ThreePThreeCModel in dumux/implicit/3p3c/3p3cmodel.hh hätten wir Implicit::ThreePThreeC::Model in dumux/implicit/3p3c/model.hh, oder statt FVPressure2P in dumux/decoupled/2p/diffusion/fv/fvpressure2p.hh hätten wir Decoupled::TwoP::Fv::Pressure in dumux/decoupled/2p/diffusion/fv/pressure.hh It would have a benefit on class and file names and a clearer identification from outside the subnamespace. The difficult task would be to decide what becomes a namespace and what not. If we can find a good solution, it would certainly pay off. Another problematic point would be that we might end with several equal filenames that get their distinction by their location, which is not be easily in, for example, editors. What do you think? Should we also go in that direction? ---------- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=214#comment517 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______________________________________________ Dumux mailing list [email protected] https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
