[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 76614] New: PRC-tools code section annotations remove function
From: Benjamin Roe <ben () benroe ! com>
Date: 2004-03-03 0:32:40
Message-ID: 20040303003240.19137.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=76614
Summary: PRC-tools code section annotations remove function from
class view
Product: kdevelop
Version: 3.0.1
Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: kdevelop-devel kdevelop org
ReportedBy: ben benroe com
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!
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic