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

List:       kwrite-devel
Subject:    [Bug 274030] Code folding should be more clever about preprocessor
From:       Rolf Eike Beer <kde () opensource ! sf-tec ! de>
Date:       2011-05-25 6:57:35
Message-ID: 20110525065735.3FDA887E4D () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=274030





--- Comment #3 from Rolf Eike Beer <kde opensource sf-tec de>  2011-05-25 08:57:34 ---
Sure, there are things that will just screw everything that does not know about
the definitions. The point is that the current way is always screwed. For me it
would be enough if the brace from one of the preprocessor blocks would be
picked, regardless which one. Adrian's suggestion would be even cooler if it is
worth the effort. Of course I'm sure someone could still screw all the things:

#define FOO
#if FOO
 if (1) {
#else
 if (0) {
 } else if (1) {
#endif

bar();

#ifndef FOO
 } else {
#else
 }
 baz();
#endif

#ifdef FOO
#undef FOO
#else
#define FOO
#endif

#ifdef FOO
 }
#endif

But I doubt this really matters. And this is really a thing that only KDevelop
can handle which is subject of bug 265225. For the moment I would be happy if
Kate would pick only one random preprocessor block and not both.

And if the new implementation has hooks where KDevelop may trap in and tell
which preprocessor block is the active one.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]