Bug#47465: indenting near preprocessor directives is bad
mitko at rila.bg
mitko at rila.bg
Thu Sep 5 11:04:02 UTC 2002
Package: kdevelop
Version: 2.1 (using KDE 3.0.0 )
Severity: normal
Installed from: SuSE RPMs
Compiler: gcc version 2.95.3 20010315 (SuSE)
OS: Linux
OS/Compiler notes: Not Specified
I have a habit to use #ifdef's to separate DEBUG-ing code in my sources and one of the problems I've got is that indenting after preprocessor directive is bad (almost none). I.e. after #ifdef or #endif I have go indent code by hand.
---------------
// Cleanup
pid_iterator = pid_vector.begin();
while (pid_iterator != pid_vector.end())
{
#ifdef DEBUG
syslog(LOG_DEBUG, "Killing process %u", * pid_iterator);
#endif
// Send signal to terminate
if (kill(* pid_iterator, SIGTERM) == -1)
-----------------
(Submitted via bugs.kde.org)
(Complete bug history is available at http://bugs.kde.org/db/47/47465.html)
More information about the KDevelop-devel
mailing list