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 632879 - Unresolved explicit link request warnings lost at 1.7.2
Unresolved explicit link request warnings lost at 1.7.2
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.2
Other Windows
: Normal critical
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-10-22 10:07 UTC by Ian.Bell
Modified: 2011-01-03 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ian.Bell 2010-10-22 10:07:39 UTC 
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
Comment 1 Dimitri van Heesch 2010-10-23 14:04:04 UTC 
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));
     }
Comment 2 Dimitri van Heesch 2011-01-03 19:01:27 UTC 
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.