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 341365 - weird "@code @endcode" bug in app-doc/doxygen-1.4.4 and 1.4.6 (1.4.5 was not tested)
weird "@code @endcode" bug in app-doc/doxygen-1.4.4 and 1.4.6 (1.4.5 was not ...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2006-05-11 03:51 UTC by Matthias Langer
Modified: 2006-06-11 08:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Matthias Langer 2006-05-11 03:51:48 UTC
What comes here are detailed instructions to reproduce a very, very subtle bug for doxygen-1.4.x. You should follow it to the point:

1.) Open the editor of your choice (or vi) and set tabstop=4.

2.) Create a header containing exactly the follwing lines:

namespace toxic {
/*!
 *  @code
 *      DoxyJam doxJam;
 *      @endcode
 */
class DoxyJam {};
}

2.) Goto line 3 and make sure that "*" is separated from "@" by two _spaces_.

3.) Goto line 5 and make sure that "*" is separated from "@" with a _tab_.

4.) Let doxygen work on this file.

You should get something like:
"test_header.h:10: File ended in the middle of a comment block! Perhaps a missing \endcode?"
and no documentation.

5.) Now goto line 3 again, remove the spaces and place a tab between "*" and "@".

6.) Run doxygen again. Voila, now it works.
Comment 1 Matthias Langer 2006-05-11 04:00:55 UTC
I've also files a bug at gentoo:
http://bugs.gentoo.org/show_bug.cgi?id=132973
Comment 2 Dimitri van Heesch 2006-06-09 18:12:42 UTC
Confirmed. Should be fixed in the next release.
Comment 3 Dimitri van Heesch 2006-06-11 08:41:23 UTC
This is an automated message triggered by a new release of doxygen.

This bug has was marked as assigned, and therefore should be fixed with the new release (1.4.7).

Please check if this is indeed the case. 
If not then please reopen the bug report.