<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 25, 2011, at 9:36 AM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div><div class="im"><div>I don't think these warnings would be suitable for Clang. </div>
</div></div></div></blockquote><div><br></div><div>Even suggesting nullptr in C++11? With things like the bool warning, NULL* used in non-pointer contexts, etc already, this seems like a fairly logical continuation/generalization of that - or would you say that, even in C++11, that it's clear that false is probably not intended as a pointer literal but still likely that someone should use 0/NULL/etc rather than nullptr?</div></div></blockquote><div><br></div><div>Just because someone is compiling with C++0x doesn't mean they want to automatically upgrade their code to C++0x.</div><br><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word"><div><div class="im"><div><br>Such style-checking transformations belong in a separate tool (e.g., like the ARC migrator).</div>
</div></div></div></blockquote><div><br></div><div>I'll have to look into how the ARC migrator works - both for the migration & for keeping code style consistent in the long term. That's part of what I was getting at - I turn on the "use nullptr" warning & then I'm never going to accidentally end up with weird uses of NULL or 0/false/etc in my code (or even in llvm's code if there was a nice way to implement some C++98 equivalent), ideally.</div>
</div></blockquote><br></div><div>I understand what you're getting at, but I consider it the domain of a separate style checker rather than something that should be implemented as a warning.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><br></body></html>