New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The line after //! within #if - #endif is ignored; C-Code (Origin: bugzilla #607736) #3641

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.6.2 on platform Other
Assigned to: Dimitri van Heesch

On 2010-01-22 08:03:53 +0000, Barbara Buth-Lhotzky wrote:

If the special comment //! is used within #if defined (..) regions, then the line following the comment is ignored. Since there are often function calls, the corresponding relations are missing in the XML and html documentation.

Here a short test program to reproduce the bug:

// main.c: Test file
#define APP_TYPE=BLH

void fctA () {};
void fctB () {};
void fctC () {};
void fctD () {};
void fctE () {};

/* FUNCTION ***********************************************/
int main(int argc, char
// normal
fctA (); // correctly recognized

#if defined(APP_TYPE) && (APP_TYPE==BLH) //! @crq _CRQ1129
//! @crq special comment
fctB (); // function call missing in doxygen documentation! BUG!!!

#if defined(APP_TYPE) && (APP_TYPE==BLH)
//! @crq special comment with blank line

fctC (); // correctly recognized

#if defined(APP_TYPE) && (APP_TYPE==BLH) //! @crq _CRQ1129
fctD (); // function call missing in doxygen documentation! BUG!!!

//! @crq _CRQ1129
fctE (); // correctly recognized

return 0;

On 2010-01-30 10:33:30 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-02-21 12:57:35 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment