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 336053 - Triple-slash comments not properly removed for \f[ and \dot
Triple-slash comments not properly removed for \f[ and \dot
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.4.x
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 487871 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-26 08:41 UTC by Dave Rahardja
Modified: 2010-10-09 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dave Rahardja 2006-03-26 08:41:37 UTC
Using triple-slash comments in C++ in conjunction with LaTeX formulas or inlined DOT graphs does not work. The triple slashes are not removed from the code passed to the LaTeX and DOT parsers.

For example, the following comment:

/** A formula.
 *  \f[
 *    x^{2} +
 *    y^{2}
 *  \f]
 */

Will generate the correct formula, i.e. x2+y2 (with appropriate superscripts).

But the following:

/// A formula.
/// \f[
///   x^{2} +
///   y^{2}
/// \f]

Will not. It generates the following instead:

///x2+///y2///

I encountered this problem in release 1.4.6-NO. The problem does not exist in release 1.4.5.
Comment 1 Dave Rahardja 2006-03-26 08:43:10 UTC
The same problem occurs with \dot...\enddot directives with triple slash comments.

Also, it doesn't matter if JAVADOC_AUTOBRIEF is ON or OFF.
Comment 2 Dimitri van Heesch 2010-08-22 18:08:56 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2010-08-22 18:09:18 UTC
*** Bug 487871 has been marked as a duplicate of this bug. ***
Comment 4 Dimitri van Heesch 2010-10-09 08:19:30 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. 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.