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 694631 - Invalid warning in conditional block
Invalid warning in conditional block
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.3.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 694632 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-02-24 23:56 UTC by john.x.foster
Modified: 2013-05-19 12:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description john.x.foster 2013-02-24 23:56:24 UTC 
BobSystem.h(17,0): warning: Member bobExport (macro definition) of file BobSystem.h is not documented.

Th following file generates this warning

/// @file

#if !defined bob_BobSystem_h
#define bob_BobSystem_h

/// @cond MSC
#if defined _MSC_VER
#define Export _declspec(dllexport)
#define Import _declspec(dllimport)
#endif
/// @endcond

		/// @cond  EXPORTS
#if defined BOBLIB_EXPORTS
#define bobExport Export
#else
#define bobExport Import // error generated here
#endif
		/// @endcond 

#endif // bob_BobSystem_h
Comment 1 Dimitri van Heesch 2013-02-25 20:23:56 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2013-02-25 20:28:14 UTC 
*** Bug 694632 has been marked as a duplicate of this bug. ***
Comment 3 Delete me 2013-04-18 15:24:12 UTC 
I can confirm the bug, happy to hear that it is fixed :-)

I see another bug that is probably related to this.

example code (written from memory):

-------------------------
///@cond priv
#define FOO bar   /**< zoo */
#define BOZO babu /**< buba */
///@endcond

void f (void)
{
   call(FOO);
}
------------------------
I get the same warning

If i put 
ENABLED_SECTIONS priv
in config I get warning: documentation for unknown define FOO found.

Can you confirm this is same bug or do i need to create new?
Comment 4 Dimitri van Heesch 2013-05-01 18:53:29 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 5 Dimitri van Heesch 2013-05-19 12:36:45 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.