"Robert Ramey" wrote:
However, sticking to one compiler is a big mistake if you want to make good code. All compilers have problems. One problem is that all pass some invalid code as valid. It fools you into thinking there's no bugs or worse, hides your bugs so you can't find them. Also C++ is so complex now (too complex?) that I can't understand the error message half the time. Then when I do I'm left wondering if it's a compiler bug or is it that I don't understand what's going on.
You are right, of course. Sorry that I exaggerated (admittedly on purpose) partly because this is fifth (if I even remember correctly) cross-platform build tool that I encounter and it won't be the first nor the last time that a parameter or a click on some checkbox in some environment resolves troubles with the 'generic' tool that may take weeks to understand and fix. But for all practical purposes I can not deny that, in my experience at least, the availability and the combination of both platform-specific and generic build tools (rather than emphasis or sticking to any of them) is the best of both worlds. So I believe that having directories with compiler-specific project files is a good idea that should be encouraged. Tony