GNOME Bugzilla – Bug 670237
#define erroneously regarded as compile guard and not documented
Last modified: 2012-02-17 08:36:00 UTC
If the construction //! \def FOO //! \brief Comment for FOO. #ifndef FOO #define FOO 1 #endif is the first one of this type in a file, the preprocessor of doxygen erroneously regards this as a compile guard by its "compile guard heuristics" and strips it away, even though it is obviously documented (and not a compile guard). This should probably be fixed by keeping the information that a define might by a compile guard together with the define and decide later on, in the main parser, whether it should be ignored (when the information from the \def is available).
I don't see how this problem is different from the previous one, so I'll mark it as a duplicate. *** This bug has been marked as a duplicate of bug 670235 ***
(In reply to comment #1) > I don't see how this problem is different from the previous one, so I'll mark > it as a duplicate. > > *** This bug has been marked as a duplicate of bug 670235 *** This is not a duplicate of bug 670235. Here, the reason for not documenting the #define is that it is regarded as a "compile guard" by the "compile guard heuristics" of doxygen. In bug 670235, the reason for not documenting the #define is in the management of the define contexts of doxygen, as described in the bug report. So two different bugs probably requiring quite different fixes.