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

List:       kde-bugs-dist
Subject:    [Bug 142551] goto next error: treat warnings as errors
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-05-25 13:18:32
Message-ID: 20070525131832.10091.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=142551         




------- Additional Comments From apaku gmx de  2007-05-25 15:18 -------
2) is not user-friendly IMHO, a goto error should go to the next error. Next error is \
whatever gcc produces as error line. As I said making the filter more complex makes \
it much slower, you have to accept a trade-off between 100% correctness and speed.

3),4) and 5) won't happen in KDevelop3/KDE3 unless you convince KDE maintainers to \
unfreeze KDE3 and write a patch for kdevelop.

As far as doing this in KDevelop4: Might be relatively easy to implement 3) there, as \
the filtering and creating special abilities for the output lines from gcc are part \
of the builder that runs the buildtool (i.e. make, scons,automake,cmake,...)


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