<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jan 30, 2014, at 16:34 , Alexander Kornienko <<a href="mailto:alexfh@google.com">alexfh@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote class="gmail_quote" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;">But maybe I'm just worried about people doing this in general, and shouldn't worry about the specific case of clang-tidy, which will probably get these answers right and be able to evolve with the analyzer core. Still, once Pandora's Box is opened, it can't easily be closed again, and we'd really like external consumers of path diagnostics to build tools that consume a standard output format rather than needing a custom build of Clang to do it.</div></blockquote><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">The difference between a tool statically linked with clang and a standalone tool consuming analyzer's output in some format is huge, and I don't think sane people would choose the former, if they only need to consumer analyzer's output in some form.</div></blockquote></div><br><div>All right, you've convinced me. I'll take a look at the names patch, but this one is fine. Let's get more analyzer users! :-)</div><div><br></div><div>Jordan</div></body></html>