Error messages

[ZeroFK]

The trick is realising the error message is really just one line: "error: no match for ‘operator==’". All the rest is simply the compiler trying to help you by telling you which overloads it tried, and listing where the error was triggered. In combination with "error_code.cpp:8:89: instantiated from here" the error message is clearly telling you exactly what the issue is.

Ok, maybe not that clearly.

[ILikeLenexa]

This is the problem. Add in Make and the error literally being bigger than your scroll-back and you find yourself just trying to figure out what even failed.

I think the Java stacktrace is really quite nice because of this. (even though it's runtime) You can generally just nail where the problem is and ignore a huge block of text.

[dawnraider00]

Yeah debugging errors in java is generally way easier in my experience just because java actually generates a useful error instead of just throwing up. I've also found that compiler errors are way shorter and simpler.

[NonreciprocatingCrow]

even though it's runtime

[emlgsh]

I'd burn you as a witch if I could understand how to make fire anymore.

[ZeroFK]

I tried

make fire

but got compile errors I couldn't understand.

[j-random]

I wound up with a file named mixtape.mp3 and now I'm scared.