<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This is not an issue with clang proper but considering the significant number of clang developers working at Apple, I thought my remark would have a better chance to be noticed here.<br><br>One of clang greatest strength is its meaningful formatting of errors. Especially invaluable is its using a marker<br><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 12px; text-indent: -12px; font: normal normal normal 11px/normal Monaco; "> return this->def(init<typename asu_parameter::scatterer_type *></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 12px; text-indent: -12px; font: normal normal normal 11px/normal Monaco; "> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 12px; text-indent: -12px; font: normal normal normal 11px/normal Monaco; min-height: 15px; "><br></div>put to pinpoint the exact position of the error in the faulty line. However XCode uses a proportional font for the "Build Results" pane, and therefore the positioning of that marker is always wrong with respect to the quoted line of code, using that very example<div><br></div><div> return this->def(init<typename asu_parameter::scatterer_type *><br> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br></div><div>Only those of you sing an email client aware of rich text would see a difference of course! but you should see the point.</div><div><br><div>That's using XCode 3.2.2 and using a script build phase to issue compilation but the same problem would happen with any other target type I think.</div><div><br></div><div>Sorry for the noise,</div><div><br></div><div>Luc Bourhis</div><div><br><br> </div></div></body></html>