Skip to content
Snippets Groups Projects
Commit f774ad6b authored by Timo Koch's avatar Timo Koch
Browse files

[changelog] const char* -> std:string may cause some compatibility issues in rare cases

parent af5acafb
No related branches found
No related tags found
Loading
...@@ -111,6 +111,10 @@ Differences Between DuMuX 2.9 and DuMuX 2.10 ...@@ -111,6 +111,10 @@ Differences Between DuMuX 2.9 and DuMuX 2.10
This is important if you implement problem classes not deriving from the base This is important if you implement problem classes not deriving from the base
problem classes in Dumux (`ImplicitProblem`, `OneModelProblem`, problem classes in Dumux (`ImplicitProblem`, `OneModelProblem`,
`ImpetProblem`, and `MultidomainProblem`). `ImpetProblem`, and `MultidomainProblem`).
- All name-related methods that previously returned / received `const char*`
do now use the type-safe alternative `std::string`. An example is
`FluidSystem::componentName()`. If you need a
`const char*` for special operation use the string member `c_str()`.
* Deprecated PROPERTY and PARAMETER NAMES, to be removed after 2.10: BEWARE: The * Deprecated PROPERTY and PARAMETER NAMES, to be removed after 2.10: BEWARE: The
compiler will not print any warning if a deprecated property or parameter name compiler will not print any warning if a deprecated property or parameter name
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment