THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#180 - Inconsistent naming - special status of saturation User who did this - Bernd Flemisch (bernd) ---------- Ok, most changes resulting from our rules that we decided today are in review. I would leave the issue of class names for the next release cycle. If we stick to our rules, this will also be a lot: everything containing FV or MPFA like FVPressure, BoxFVElementGeometry, FVMPFAOInteractionVolume and so on. And also everything containing 2P/2C/NI like TwoPNIModel, CellData2P and so on. One group is left: chemical component names like CO2, H2O, N2 and so on. This would become, for example, co2Idx or fugacityCoefficientCo2. Should we stick to our rules or make an exception? I tend to \"stick.\" ---------- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=180#comment350 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
