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 752712 - last entry missing in a @name group of typedefs
last entry missing in a @name group of typedefs
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.10
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-07-22 11:59 UTC by thomas.schmalholz
Modified: 2017-03-27 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
doxygen config file (12.49 KB, text/plain)
2015-07-22 11:59 UTC, thomas.schmalholz
Details
example 1 (331 bytes, text/plain)
2015-07-22 12:01 UTC, thomas.schmalholz
Details
screenshot of output of example1 with doxygen 1.8.11 (43.94 KB, image/jpeg)
2016-01-29 09:41 UTC, thomas.schmalholz
Details

Description thomas.schmalholz 2015-07-22 11:59:27 UTC
Created attachment 307903 [details]
doxygen config file

When I run doxygen to create a html output for the following C example, the type UW_16 is missing.

example 1: UW_16 is missing in the output --->
                                     ///@name definition of all integer and boolean types as standard
                                     ///@{
typedef uint8_t             UB__8;   ///<  8 bit unsigned data type
typedef uint16_t            UW_16;   ///< 16 bit unsigned data type
                                     ///@}
<--- example 1

If I insert an empty line before the closing braket, it works fine.

example 2: works fine --->
                                     ///@name definition of all integer and boolean types as standard
                                     ///@{
typedef uint8_t             UB__8;   ///<  8 bit unsigned data type
typedef uint16_t            UW_16;   ///< 16 bit unsigned data type

                                     ///@}
<--- example 2

The same issue does _not_ occur, if it were defines instead of typedefs.

Thank you for your consideration.
Comment 1 thomas.schmalholz 2015-07-22 12:01:29 UTC
Created attachment 307904 [details]
example 1
Comment 2 Dimitri van Heesch 2015-07-26 13:18:08 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2015-12-30 10:19:57 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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 (preferably in the form of a self-contained example).
Comment 4 thomas.schmalholz 2016-01-29 09:37:54 UTC
I tested the changes with the already attached 'example 1'. With doxygen version 1.8.11, the missing typedef is now visible, but it's comment is still missing.
Comment 5 thomas.schmalholz 2016-01-29 09:41:09 UTC
Created attachment 320004 [details]
screenshot of output of example1 with doxygen 1.8.11

screenshot of output of example1 with doxygen 1.8.11
Comment 6 Dimitri van Heesch 2016-02-06 15:33:45 UTC
Confirmed. The comment was not missing, just shown as a detailed description, because it was seen as a multi-line ///-style comment.

Should be fixed in the next GIT update, where I'll treat lines with @} markers specially.
Comment 7 Dimitri van Heesch 2016-09-05 13:45:48 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).
Comment 8 thomas.schmalholz 2017-03-27 13:54:05 UTC
I tested with doxygen version 1.8.13 and it works fine. Thank you for your help.