<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Aug 20, 2014, at 11:58 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com" class="">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">I'm glad to hear that there is a desire to improve this situation.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">However, I want to point out what seems like very flawed reasoning to me:</div>
<div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Aug 20, 2014 at 10:43 AM, Kate Stone <span dir="ltr" class=""><<a href="mailto:katherine_stone@apple.com" target="_blank" class="">katherine_stone@apple.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We shouldn’t be arbitrarily different, and where we do differ we should be able to describe the specific rationale (as I’m sure Greg will gladly do when it comes to line length and naming conventions.)</blockquote>
</div><br class=""></div><div class="gmail_extra">Unfortunately, if you're going to differ whenever you have a specific rationale, it undermines the benefit of matching the LLVM style at all.</div></div></div></blockquote><div><br class=""></div><div>That’s not exactly what I was suggesting. It’s important to recognize that there is a substantial body of code already written. It’s impractical to spend time and energy reformatting and renaming everything. New code should fit in with old, but where it’s already inconsistent there’s an immediate opportunity to start conforming to LLVM’s established style for new contributions. So the goal isn’t to diverge whenever there’s a rationale for doing so, but to require that established style is documented sufficiently.</div><div><br class=""></div><div>I disagree that there’s no value in conforming to any of LLVM’s style guidelines. We should minimize the amount that someone needs to learn to contribute productively to both projects. Over time, with advocates involved in both, I would like to move toward more conformity – but that’s very much up to active contributors to determine. I happen to have some pull with the most active but I also have a lot of respect for the time and energy they have put into the project to date.</div></div><div><br class=""></div><div><div class="" style="font-family: LucidaGrande; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><font color="#424242" class="" style="font-family: 'Lucida Grande'; font-size: x-small;">Kate Stone</font><span class="" style="font-family: 'Lucida Grande'; font-size: x-small;"> </span><font color="#009193" class="" style="font-family: 'Lucida Grande'; font-size: x-small;"><a href="mailto:k8stone@apple.com" class="">k8stone@apple.com</a></font></div><div class="" style="font-family: Times; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><font face="Lucida Grande" size="1" class=""><font color="#009193" class=""></font> Xcode <font color="#424242" class="">Runtime Analysis Tools</font></font></div></div><br class=""></body></html>