[Development] Upgrading the sources to C++11 keywords (Q_NULLPTR, etc.)

Thiago Macieira thiago.macieira at intel.com
Thu Feb 12 04:06:39 CET 2015

On Wednesday 11 February 2015 18:05:09 Matthew Woehlke wrote:
> > Only if we build with -Werror -- which we do, in the compilers that
> > support  __null.
> Um... do you not have *any* C++11 builds? If Q_NULLPTR == nullptr (which
> I assume it is in C++11?), and you try to pass Q_NULLPTR to something
> that wants an integer type, you'd better get a compile error, because
> such a conversion is not allowed by the C++ standard. (At least
> gcc-c++-4.8.3-7.fc20.x86_64 correctly rejects this.)

You're right...

All the compilers that support __null and that we test also support C++11 and 
nullptr, so we wouldn't get the __null warning converted to error, we'd get 
the actual nullptr error.
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list