3 ms·
Personally I rarely look at the actual gcc error messages, because most of the time they are useless. I just note the line number and directly look at the code.
by petsos 17y ago
Personally I rarely look at the actual gcc error messages, because most of the time they are useless. I just note the line number and directly look at the code.
- ajuc 17y agoYou are too cruel to poor gcc. They are no useless, you just have to remember which combination of messages having nothing to do with your code could be caused by what sort of errors. Gcc makes sure we will remember these rules better by making it painful and thus more vivid in memories. Also - real fun begins, when you forgot semicolon after the class definition in your header, and error shows in different file.
- leif 17y agoThey aren't useless, they're just unclear. They map pretty well to actual issues, and after a while you'll get used to translating them.