On Fri, Jan 23, 2015 at 12:55 PM, Konstantine Rybnikov wrote:
Tuncer,
If warnings will be treated as errors it's fine to have "Error:" shown for them, I think.
Yes, it will be printed the same way and have the same severity as any other error. I think I have misinterpreted your initial post, sorry about that. To correct myself, compilers do print "error:" prefixes, and for example your usual CC will print the following: filename:row:column: error: error-message filename:row:column: warning: warning-message So on second thought your suggestion makes sense :).
On Fri, Jan 23, 2015 at 1:14 PM, Tuncer Ayaz wrote:
On Fri, Jan 23, 2015 at 12:04 PM, Konstantine Rybnikov wrote:
Hi!
I'm bringing this up once again. Can we add "Error:" in the output of an error in a similar way ghc shows "Warning:" for warnings? Main reasoning is that, for example, on a build-server, where you have lots of cores to build your program, if you get an error, it gets lost somewhere in the middle of compiler's output in all other "Warning" messages you get, since error is not always shown last on multi-core build.
Isn't kind of a compiler convention that ""Warning:" is only prepended if an issue is treated as a warning. I mean, you can enable -Werror and treat all or specific warnings as errors as well.