[Development] RFF: nullptr rules

Marc Mutz marc.mutz at kdab.com
Wed Dec 9 22:47:51 CET 2015

On Wednesday 09 December 2015 19:11:29 Thiago Macieira wrote:
> 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;

What we agreed on was for Q_NULLPTR.

Some developers back then were complaining that the *macro* is ugly, and that 
by 5.7, we would be able to use the real thing and didn't want the double 
conversion 0 -> Q_NULLPTR -> nullptr.

The agreement back then also was not to rely on the disambiguating features of 
nullptr, because Q_NULLPTR might be 0.

Now we can use the real thing. With real nullptr semantics.


Marc Mutz <marc.mutz at kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts

More information about the Development mailing list