[Development] RFF: nullptr rules
Thiago Macieira
thiago.macieira at intel.com
Wed Dec 9 19:11:29 CET 2015
On Wednesday 09 December 2015 16:14:00 Marc Mutz wrote:
> - 0 as a nullptr constant is banned except in tests testing APIs so
> we don't accidentally require nullptr (ie. all tests should use 0, not
> nullptr, as far as it makes sense)
This is not what we had agreed to.
We had said that where it's unambiguous, we can still use 0, outside of public
headers.
const char *ptr = 0;
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list