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

List:       kde-bugs-dist
Subject:    [Bug 132643] Make member does not work with multiple defines
From:       Angus <sylvania25 () videotron ! ca>
Date:       2007-06-20 20:18:39
Message-ID: 20070620201839.11047.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=132643         




------- Additional Comments From sylvania25 videotron ca  2007-06-20 22:18 -------
It should be changed such that the red line doesn't appear unless there truly is a \
syntax error. If there's any chance at all that the line in question might not \
generate an error for the designated language, I think it should give the programmer \
the benefit of the doubt.  Why are macros bad? They are bad if you try to use them as \
functions in C++, but in one case, I have little choice. I've got a pure virtual that \
I want to assign an __attribute__((fastcall)) to. That attribute is meaningless if \
building for x86-64, but useful in i386. Furthermore, if I ever decide to take away \
that fastcall for all environments, then I'd have to hunt down every override, \
because if you neglect to assign the proper calling convention, Gnu does *not* \
generate a compile error, but you'll have a very obscure bug at run-time.

    And I did try adding the macro to C++ Parsing, and it still red-lines the code.


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