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 709870 - Broken links on members HTML page when using BUILTIN_STL_SUPPORT
Broken links on members HTML page when using BUILTIN_STL_SUPPORT
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-10-10 23:35 UTC by Ben Webb
Modified: 2013-12-24 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
dox.tar.gz (2.97 KB, application/x-gzip)
2013-10-10 23:35 UTC, Ben Webb
Details

Description Ben Webb 2013-10-10 23:35:17 UTC
Created attachment 256960 [details]
dox.tar.gz

Given a simple input file, inputs/test.h (also in the attachment):
#include <vector>

//! Test class
template<class ValueT>
class Test : public std::vector< ValueT > {
};

and a simple doxygen config that differs from the output of 'doxygen -s' only by
BUILTIN_STL_SUPPORT    = YES
INPUT                  = inputs
FILE_PATTERNS          = *.h
GENERATE_LATEX         = NO

the output HTML file classTest-members.html contains an entry for an 'elements' member in the class, inherited from std::vector. It looks a little like:

elements (defined in std::vector< T >)                  std::vector< T >

The text in the first column is fine (other than the member being there in the first place - I don't think std::vector has an 'elements' member). But the second column is a hyperlink, to classstd_1_1vector.html. This file doesn't exist.

Ideally, the std::vector< T > in the second column would be unlinked, same as that in the first column.
Comment 1 Dimitri van Heesch 2013-10-12 11:34:41 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2013-12-24 18:59:21 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).