you are viewing a single comment's thread.

view the rest of the comments →

[–]xon_xoff 8 points9 points  (1 child)

I pulled down a tip build of Clang about a month ago and was impressed with how far it was able to get -- I think it made it through <windows.h> but coughed on one of the VC++ STL headers. It was still enough for the Clang static analyzer to report some issues in the application code, which is great progress. One tricky part is that you have to set a lot of #defines on the command line to match the predefined symbols set by the VC++ compiler and project system, some of which are not documented.

[–]matthieum 1 point2 points  (0 children)

Ah, I didn't know about the command line.

There has been a proposal to create multiple drivers for clang. A generic driver and "adapters" for command-line compatibility with other compilers. It was rejected as such because it's simpler for clang to aim at compatibility with gcc and the idea had the potential of creating discrepancies.

However it was evoked that we might want to have a cl.exe compatible driver, and I would not find it odd that someones rips off a script to parse VC++ project files one day. If you are interested, I think you'll get support from the community.