NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

User Hostile (Score:1)

by chromatic (983)

C++ is perhaps not the best example of scrutable error messages from compilers. (The single design decision in C++ with which I can wholeheartedly agree is "You don't pay for what you don't use. I'm not sure C++ always lives up to that in terms of the conceptual tax, however.)
intel c++ seems smarter (Score:1)

by tonyc (123)

Of course, not all compilers are stupid enough to leave the error reporting until assembly time:
tony@mars:~/play$ icpc test.cpp test.cpp(11): error: "Foo" has already been declared in the current scope namespace Foo { ^ compilation aborted for test.cpp (code 2)
Debugging symbols (Score:2)

by drhyde (1683)

Is it less inscrutable if you build with -g? Which, of course, the sensible C/C++ programmer will be doing anyway during development.
Wait, what am I saying? A sensible C hacker? Hah!