<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 30, 2011, at 2:19 AM, Sean Hunt wrote:</div><blockquote type="cite"><div>On 11-05-30 02:15 AM, John McCall wrote:<br><blockquote type="cite">On May 30, 2011, at 2:07 AM, Nikola Smiljanic wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Hi all,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">If somebody would explain the difference between clang and clang++. I downloaded 2.9 release and clang.exe and clang++.exe are identical files?<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Invoking the compiler as clang++ requests it to compile and link code as C++. This typically only matters when linking object files, where it causes the C++ standard library to be linked in.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I don't know why (or whether) these files are independent on disk; on Unix-y platforms, clang++ is just a symlink.<br></blockquote><font class="Apple-style-span" color="#006312"><br></font>They might be hard linked?<br></div></blockquote></div><br><div>I had the impression that the Windows filesystem was sane enough to not allow hard-linking, but I am prepared to be corrected.</div><div><br></div><div>I rate it more likely that some packager just didn't want to deal with symlinks.</div><div><br></div><div>John.</div></body></html>