| Summary: | indenting near preprocessor directives is bad | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | mitko |
| Component: | kdevelop 2.x (obsolete) | Assignee: | KDevelop-Devel List <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 2.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
This is handled by the embedded editor in Gideon, and Kate should do this better. |
(*** This bug was imported into bugs.kde.org ***) 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)