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

Invalid warning in conditional block (Origin: bugzilla #694631) #5092

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

On 2013-02-24 23:56:24 +0000, john.x.foster@nab.com.au wrote:

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

On 2013-02-25 20:23:56 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-02-25 20:28:14 +0000, Dimitri van Heesch wrote:

*** Bug 694632 has been marked as a duplicate of this bug. ***

On 2013-04-18 15:24:12 +0000, mah@danfoss.com wrote:

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?

On 2013-05-01 18:53:29 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-05-19 12:36:45 +0000, Dimitri van Heesch wrote:

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.

@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