| Summary: | PRC-tools code section annotations remove function from class view | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Benjamin Roe <ben> |
| Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | 3.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
OK, ignore me, found the C++ parsing options page. Sorry. |
Version: 3.0.1 (using KDE KDE 3.2.0) Installed from: Gentoo Packages Compiler: gcc 3.3.2 OS: Linux A bit of an obscure bug - more of a wish, really. In PalmOS development it is necessary to put functions into different code sections in order to avoid the limitations of 16-bit jumps and allow >32k jumps. To do this, the code section is specified after the function declaration. For example: void foo(UInt16 bar) __attribute__ ((section ("filefns"))); would put foo in the "filefns" section. To make it easier to type, I normally do: #define FILE_SECTION __attribute__ ((section ("filefns"))) but if I try to specify a function like this: void foo(UInt16 bar) FILE_SECTION; it isn't shown in the class view. If I type the declaration in full, it is shown, only the version using the #define isn't. Is there any way the #defined version could be made to work with the class view? I imagine parsing all preprocessor directives might be a bit too complex to do every time the class view is updated though!