[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 265225] New: Code folding get's confused by preprocessor defines
From: Rolf Eike Beer <kde () opensource ! sf-tec ! de>
Date: 2011-02-02 19:37:01
Message-ID: bug-265225-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=265225
Summary: Code folding get's confused by preprocessor defines
Product: kdevelop
Version: 4.2.0
Platform: openSUSE RPMs
OS/Version: Linux
Status: NEW
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs@kdevelop.org
ReportedBy: kde@opensource.sf-tec.de
Created an attachment (id=56796)
--> (http://bugs.kde.org/attachment.cgi?id=56796)
Folding vs. preprocessor testcase
Version: 4.2.0 (using KDE 4.6.0)
OS: Linux
If I have a preprocessor #if/#else/#endif and open a code block (like "if ()
{") in both of them that is closed outside the preprocessor block the folding
logic doesn't take the preprocessor block into account, i.e. it ignores the
fact that only _one_ of those blocks can actually be in use. That leads to the
fact that the folder miscounts the number of braces and folds completely wrong.
Reproducible: Always
Steps to Reproduce:
See attached example.
Expected Results:
The inactive preprocessor block should allow code folding only within itself.
KDevelop usually knows which one is active and which not so this shouldn't be a
problem. With only one block taken as active the folding would be correct.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic