News for hackers. Stuff that matters.
Re:Results of the Grand C++ Error Explosion Competition by coherentpony on Sunday January 26, 2014 @10:40PM (#7128649)
s/C++/g++/

clang++ isn't nearly as bad.

Re:Results of the Grand C++ Error Explosion Competition by InclinedPlane on Sunday January 26, 2014 @10:45PM (#7128660)
I tried some of the examples with g++/cc and with clang. Clang is a lot better but it still produces some pretty ridiculous output (but not gigs of ridiculous output fortunately).
Re:Results of the Grand C++ Error Explosion Competition by coherentpony on Sunday January 26, 2014 @10:49PM (#7128670)
Oh, I totally agree. That said, these examples are engineered to make your compiler shit a brick. Most of the time clang++ gives you much more readable output. g++, however, is a lot more careful about your digits. It'll take a little while before clang++ gains serious traction in the scientific community.
Re:Results of the Grand C++ Error Explosion Competition by rwallace on Monday January 27, 2014 @06:14AM (#7129761)
> g++, however, is a lot more careful about your digits. It'll take a little while before clang++ gains serious traction in the scientific community.

How do you mean? Does clang have some sort of problem with numeric precision?

Re:Results of the Grand C++ Error Explosion Competition by exDM69 on Monday January 27, 2014 @03:49AM (#7129426)
g++ has improved their error messages in the past few years, especially when it comes to template error messages. But C++ is still really complicated and you can get get pretty nasty errors.

And clang++ may be better in some aspects but it is not perfect either, one of the entries in this contest caused clang++ to segfault.