[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 142551] goto next error: treat warnings as errors
From:       Premysl Paska <premek.paska () gmail ! com>
Date:       2007-07-09 10:41:28
Message-ID: 20070709104128.10798.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=142551         




------- Additional Comments From premek.paska gmail com  2007-07-09 12:41 -------
I agree with everyone saying that "Next Error" command should jump to next error; \
nevertheless I claim that the "fix" was unfortunate.

Who said that this was the only way to fix the inconsistency? Why not to rename the \
menu entries to "Next Error or Warning" and "Previous Error or Warning"?

Personally I have always used the F4 key (shortcut for Next Error) to search for \
warnings and never used it to search for errors. I think that there is no need to \
search for errors, because compilation stops after couple of errors (at least in the \
default settings) and it's sufficient to examine bottom of the output. On the other \
hand warnings are usually spread throughout - typically very long - output and it is \
extremely uncomfortable to track them out manually.

Also I strongly disagree with the theory presented above that vast majority of \
programmers totally ignore warnings (and that it was the reason for the change). For \
me such a programmer is not a programmer at all. In C/C++ it is suicide to ignore all \
warnings.

Was someone requesting the change? Was there a bug for this? The commit doing the  \
change doesn't say so (http://lists.kde.org/?l=kde-commits&m=115498536419227&w=2, \
commit 570855). 

Now I'm thinking of downgrading back to 3.3 or better patching 3.4 using reverse of \
the diff from the commit (David, have I found the right change?).

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


[prev in list] [next in list] [prev in thread] [next in thread]