GNU has gotten quite a bit better with that. I use clang as an alternative and the clang-analyzer is amazing.
Any complicated STL error will show some serious jargon in any compiler. There is no working around it since to present all the information necessary to fix that error, that jargon is necessary. Possibly one reason why I'm closer to C in later days lol.
I actually love it when that sort of things happens. The more errors I get makes me feel more like a programmer than getting it to work out of the gate. I love the errors that say it is on line 124, you trace it back and find the error came from like line 18.
@ IWishIKnew: There should be a setting for your IDE to fail at the first error. I'm pretty sure it's an argument that gets passed onto the linker\compiler.
Personally, I'm like Albatross. If you were to randomly pick a source code file from my projects folder you would think that I'm one of those people who can't complete a sentence without swearing. Luckily Find and Replace fixes this issue for me rather quickly if I ever have to submit my code (not that anyone ever reads it).