[Bug 60512] Syntax parser can be fooled by #defines

[Dominik Haumann]

On Tuesday 08 February 2005 16:47, Roberto Raggi wrote:
> 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).
Can you give an example of how the a macro has to look like in this editbox?
a simple BLUBB() doesn't do anything. A WhatsThis is missing here and nobody 
could explain it to me yet! :) Maybe you can enlighten me *hope* :)

Cheers,
-- 
Dominik
GPG Fingerprint: AC88 49E3 D8A5 0541 5B71 AC6E 29AA 1696 FF64 EDBC
User-Agent: KMail; Desktop: KDE; OS: Gentoo/Linux; *free software*
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20050208/316b655f/attachment.sig>