#904 nullptr compatibility code is incompatible with GCC 4.6
Metadata
| Property | Value |
|---|---|
| Reported by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
| Reported at | Apr 7, 2011 12:38 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Sep 6, 2011 17:05 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Sep 6, 2011 17:05 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | fixed in dune-common r6492 |
Description
The nullptr compatibility wrapper in dune-common does not work correctly with GCC 4.6. The problem is that the wrapper is based on an older draft of C++0x, while GCC 4.6 implements nullptr according to the latest draft. The difference between the two draft versions is that nullptr_t was moved into namespace std and requires inclusion of .
The attached patch fixes the configure test and includes the required header in nullptr.hh if compiler support is detected, but I don't know exactly what to do about nullptr_t - do it like tuple, array etc. and import the definition into the Dune namespace?