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

Unresolved explicit link request warnings lost at 1.7.2 (Origin: bugzilla #632879) #3989

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 critical in component general for ---
Reported in version 1.7.2 on platform Other
Assigned to: Dimitri van Heesch

On 2010-10-22 10:07:39 +0000, Ian.Bell@autodesk.com wrote:

If #include blah
(or #if or any C-preprocessor command ) is parsed by doxygen not inside a \code ... \endcode than the # is interpreted as forcing an explicit link to include.
In 1.6.3 this resulted in a
'Warning: explicit link request to 'include' could not be resolved' warning.
In 1.7.2 there is no warning, and include with the # stripped is added to the output documentation.

If warnings are used for quality-control, this absence is unacceptable. Workaround is to stay on 1.6.3

On 2010-10-23 14:04:04 +0000, Dimitri van Heesch wrote:

Confirmed.

The fix is straightforward:

--- ../../doxygen-svn/src/docparser.cpp 2010-10-08 21:51:57.000000000 +0200
+++ docparser.cpp 2010-10-23 15:59:41.000000000 +0200
@@ -1104,7 +1104,7 @@
}
else // normal non-linkable word
{

  • if (g_token->name.left(1)=='#' || g_token->name.left(2)=="::")
  • if (g_token->name.left(1)=="#" || g_token->name.left(2)=="::")
    {
    warn_doc_error(g_fileName,doctokenizerYYlineno,"warning: explicit link request to '%s' could not be resolved",qPrint(name));
    }

On 2011-01-03 19:01:27 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.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