#670 Remove obscure "DUNE developer mode"
Metadata
| Property | Value |
|---|---|
| Reported by | Sven Marnach (sven@pantoffel-wg.de) |
| Reported at | Nov 26, 2009 13:33 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Feb 9, 2011 20:33 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Feb 9, 2011 20:33 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | in dune-common r6334 |
Description
configure has a flag called --enable-dunedevel. The "documentation" of this flag says
--enable-dunedevel activate Dune-Developer-mode
This mode appears to do two things:
-
Activate some Barton-Nackman interface checks as long as NDEBUG is not defined.
-
Output some additional information if an exception is thrown (file, line, function)
I would just remove this mode. 1. can also be switched on and off by the NDEBUG switch. 2. can just be switched on always -- it is expensive anyway to throw an exception. Additionally, instead of writing the additional information to a string stream, we could just use the preprocessor to "stringify" the information at compile time.
In case the DUNE developer mode is going to stay, it should at least be documented.