[webkit-dev] Guideline for nullptr

Dan Bernstein mitz at apple.com
Mon Jan 6 12:01:26 PST 2014

Sent from my iPad

> On Jan 6, 2014, at 11:55 AM, Darin Adler <darin at apple.com> wrote:
> I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in WebKit C++ sources. I don’t see any advantage to using 0 or NULL over nullptr, and nullptr has multiple advantages. Three obvious ones: Compile time error if accidentally passed to something expecting an integer, can be distinguished from an integer in function overloading, can tell it’s a pointer.
> Any objections?
> — Darin
> PS: Maybe even instead of nil in WebKit Objective-C++ code?

In Objective-C++, nil is nullptr, so I suggest that we stick with the language convention of writing it as nil.

More information about the webkit-dev mailing list