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

List:       kdevelop-devel
Subject:    Re: [Bug 60512] Syntax parser can be fooled by #defines
From:       Roberto Raggi <roberto () kdevelop ! org>
Date:       2005-02-08 15:47:51
Message-ID: 200502081647.51416.roberto () kdevelop ! org
[Download RAW message or body]

well, actually all these examples are pretty useless! KDevelop doesn't parse 
the files in order. It doesn't respect the #include directive. If you want to 
use macros you have to "Configure the parser". It is almost impossible to 
parser the files in order without *support* from the build system.

Open "Configure KDevelop", select "C++ Parser" and define your own macros. It 
works for me, but I'm using a pretty old version of KDevelop(3.0.x).

ciao robe


On Tuesday 08 February 2005 16:37, Daniel Franke wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=60512
>
>
>
>
> ------- Additional Comments From daniel.franke imbs uni-luebeck de 
> 2005-02-08 16:37 ------- Another try ...
>
> > bug.h
>
> #define BUG_ATTRIBUTES __attribute__ ((noreturn, format (printf, 1, 2)))
> void bug(const char *fmt, ...) BUG_ATTRIBUTES;
>
> > bug.c
>
> #include "bug.h"
> void bug(const char *fmt, ...) BUG_ATTRIBUTES {    // <-- Syntax Error
> reported }
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel@barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]