After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607736 - The line after //! within #if - #endif is ignored; C-Code
The line after //! within #if - #endif is ignored; C-Code
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.2
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-01-22 08:03 UTC by Barbara Buth-Lhotzky
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Barbara Buth-Lhotzky 2010-01-22 08:03:53 UTC
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* argv[])
{
  // normal
  fctA ();	// correctly recognized
  
#if defined(APP_TYPE) && (APP_TYPE==BLH)  //! @crq _CRQ1129 
  //! @crq special comment
  fctB ();	// function call missing in doxygen documentation! BUG!!!
#endif  


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

  fctC ();	// correctly recognized
#endif

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

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

  return 0;
}
Comment 1 Dimitri van Heesch 2010-01-30 10:33:30 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2010-02-21 12:57:35 UTC
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.