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 626799 - Documentation using //! not generated correctly
Documentation using //! not generated correctly
Status: RESOLVED DUPLICATE of bug 625952
Product: doxygen
Classification: Other
Component: general
1.7.1
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-08-13 09:30 UTC by pk
Modified: 2010-08-14 14:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Doxygen input / output + configuration (49.44 KB, application/zip)
2010-08-13 15:46 UTC, pk 		Details

Description pk 2010-08-13 09:30:44 UTC 
Description:

I'm using long time //! documentation comments and it worked almost fine. Now with version 1.7.1 the document generation is broken. Doxygen don't generate detailed section and everything is in @brief section including the //! comments.

Solution:

Parse correctly //! comments.

Example (C++):

//! @brief My class.
//!
//! My class provides interaction between A and B.
class MyClass
{
}

The documentation generated:

<brief section>
My class. //! //! My class provides interaction between A and B.

<detailed section>
NONE
Comment 1 Dimitri van Heesch 2010-08-13 15:39:06 UTC 
I have not been able to reproduce the problem with the example provided. Can you please attach a self-contained example (source+config file in a tar or zip) for which you verified it contains the problem?
Comment 2 pk 2010-08-13 15:46:33 UTC 
Created attachment 167817 [details]
Doxygen input / output + configuration
Comment 3 pk 2010-08-13 15:48:20 UTC 
I added an attachment, there is simple input file, doxygen configuration I'm using and the output generated by doxygen. Click to CLASSES.

Thanks for your fast reply
Comment 4 Dimitri van Heesch 2010-08-13 15:57:36 UTC 
Thanks for the example. The problem seems to be related to the MULTILINE_CPP_IS_BRIEF setting.
Comment 5 Dimitri van Heesch 2010-08-14 14:12:13 UTC 

*** This bug has been marked as a duplicate of bug 625952 ***