------- Comment #11 from paolo dot carlini at oracle dot com 2009-11-04 20:18 ------- (In reply to comment #10) > At least that way you'll know the error is always at the top, instead of at > some point between the end of the compile line and the next prompt.
Yes, but is this true with -Wfatal-errors? Maybe I should just take the time to experiment a bit more, but the reason why I posted my mumblings last night, is that it occurred to me that probably it's simply not true with -Wfatal-errors, that is, the single error is always exactly the last printed thing, close to the new prompt. For example, take the messages in your Comment #7, and imagine for a moment each is 50 lines, not uncommon with templates, which one would be more quickly informative in your ~30 lines window? That said, I agree there are also reasons to reason: first print the error, and then all the additional details, this strategy being very effective for short overall messages, fitting in the window. However, I don't think all the users of GCC can agree, or in large majority at least, about which one is best. In conclusion, my current idea is: either have a switch to choose case by case, or give the issue a bit more thought before changing a very old behavior. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41884
