<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 29, 2012, at 2:05 PM, Manuel Klimek <<a href="mailto:klimek@google.com">klimek@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Fri, Jun 29, 2012 at 10:40 PM, Douglas Gregor <span dir="ltr"><<a href="mailto:dgregor@apple.com" target="_blank">dgregor@apple.com</a>></span> wrote:<br><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">CamelCase is fine for these. I notice that there's some inconsistency with 'has' names, e.g., hasDescendant vs. HasType.</div></blockquote><div><br></div><div>Update: Chandler voted for using llvm coding style (and I agree). The argument is that the callable classes we have are just classes to work around missing variadic templates and that they will become functions anyway once we get C++11 into llvm (in a future, far, far away).</div>
</div></blockquote><br>Works for me.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br></div><br></body></html>