last entry missing in a @name group of typedefs (Origin: bugzilla #752712)

[doxygen]

status RESOLVED severity normal in component general for ---
Reported in version 1.8.10 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

• doxygen (ID 307903)
• example1.h (ID 307904)
• output_example1.jpg (ID 320004)

On 2015-07-22 11:59:27 +0000, thomas.schmalholz@hilti.com wrote:

Created attachment 307903
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.

On 2015-07-22 12:01:29 +0000, thomas.schmalholz@hilti.com wrote:

Created attachment 307904
example 1

On 2015-07-26 13:18:08 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2015-12-30 10:19:57 +0000, Dimitri van Heesch wrote:

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).

On 2016-01-29 09:37:54 +0000, thomas.schmalholz@hilti.com wrote:

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.

On 2016-01-29 09:41:09 +0000, thomas.schmalholz@hilti.com wrote:

Created attachment 320004
screenshot of output of example1 with doxygen 1.8.11

screenshot of output of example1 with doxygen 1.8.11

On 2016-02-06 15:33:45 +0000, Dimitri van Heesch wrote:

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.

On 2016-09-05 13:45:48 +0000, Dimitri van Heesch wrote:

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).

On 2017-03-27 13:54:05 +0000, thomas.schmalholz@hilti.com wrote:

I tested with doxygen version 1.8.13 and it works fine. Thank you for your help.