On 16/11/2015 at 05:01, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Hehe, I'm going to disagree with you there Wilfried. Xcode may be a better compiler, I'm not qualified to judge, but as a user experience it falls well short IMO. The editor is odd and seems flaky to me, Visual Assist X is VS-only and I don't like to code without that, and error messages don't seem clear to me at all. Especially linker errors, they are totally impenetrable.
But in the end we all have to use both anyway, so it comes down to personal preference I guess, which one you use for primary development.
You'd have to pick the right tool for the job - as always; I think it helps and improves your product when you're familiar with more than one development environment:
- You have an easy debugging job (need to watch some variables, etc.) : use MSVC
- Need to debug very custom code and data structures: Think about extending the python based debugging in Xcode
- Have to fix 40000s warnings in several thousand files: Use Xcode due to shear compile speed, better warnings (and the ability to check your code for warnings before you do a full compile)
- Need to look at the bare metal of your gpu: Use MSVC with the tools offered by gpu vendors
- Need static code analysis to find logic erros in your code: Use Xcode instead of shelling out several thousand dollars for MSVC 3rd party tools.
If you're creating a lot of templates code, the advantages of Clang (Xcode) or gcc over MSVC should be obvious. The later one usually creates dozens of misleading error messages (if its able to properly handle c++ compliant template code at all). Regarding linker messages: Usually looking at the output of the of linker should give you enough hints to see what was going on.