<div dir="ltr">Sounds like a great idea to me.</div><div class="gmail_extra"><br clear="all"><div>- R. Niwa</div>
<br><br><div class="gmail_quote">On Mon, Jan 6, 2014 at 12:04 PM, Anders Carlsson <span dir="ltr"><<a href="mailto:andersca@apple.com" target="_blank">andersca@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Jan 6, 2014, at 12:01 PM, Dan Bernstein <<a href="mailto:mitz@apple.com">mitz@apple.com</a>> wrote:<br>
<br>
><br>
><br>
> Sent from my iPad<br>
><br>
>> On Jan 6, 2014, at 11:55 AM, Darin Adler <<a href="mailto:darin@apple.com">darin@apple.com</a>> wrote:<br>
>><br>
>> 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.<br>
>><br>
>> Any objections?<br>
<br>
</div>I think this is a great idea and something I’ve been doing ever since nullptr became available to us.<br>
<div class="im"><br>
>><br>
>> — Darin<br>
>><br>
>> PS: Maybe even instead of nil in WebKit Objective-C++ code?<br>
><br>
> In Objective-C++, nil is nullptr, so I suggest that we stick with the language convention of writing it as nil.<br>
<br>
</div>I agree. (Also, using Nil for null classes).<br>
<span class="HOEnZb"><font color="#888888"><br>
- Anders<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</div></div></blockquote></div><br></div>