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

List:       kdevelop-bugs
Subject:    [Bug 168537] Report unused includes in C++
From:       Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date:       2008-08-06 21:43:32
Message-ID: 20080806214332.1451.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=168537         




------- Additional Comments From jens.dagerbo swipnet se  2008-08-06 23:43 \
------- Warnings about unneeded includes and perhaps even user initiated \
automated cleanup are nice features, but under no circumstances should \
KDevelop automatically remove or change the code. Not even based on a \
setting. An application that makes educated guesses will eventually get it \
wrong and that really destroys the user's confidence in the application.

It's quite easy to think of scenarios where removing an unneeded include \
would be the wrong thing to do: What if the "#include <QLabel>" line is all \
I've written thus far in a file? It's clearly not "needed" by any code yet, \
but I don't expect to have it removed because of this.

Simplyfying include statements like Andreas suggests in #1 is generally a \
cool thing, but again it could well be the wrong thing to do in some cases. \
A multi layer include setup could well be by design. Think for instance of \
Qt, where "#include <QLabel>" only in turn includes a file called \
"qlabel.h". This does not mean that the code should contain "#include \
<qlabel.h>".

_______________________________________________
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]