Variadic macro expansion with comments

[kanje]

This is somewhat an extension to #8542.

I want to use inline comments to document enum values defined with a macro such as

/**
 * Enum with values.
 */
ENUM(Values,
    Value1, ///< First value.
    Value2, ///< Second value.
);

I did

PREDEFINED = "ENUM(t,...)=enum class t { __VA_ARGS__ }"

and this is what I am getting with doxygen -d preprocessor:

/**
 * Enum with values.
 */

///< First value.
///< Second value.
 enum class  Values  {  Value1,              Value2  };

I tried this with both Doxygen 1.9.5 and the latest master (1.12.0) --- the result is the same.

Would it be possible to somehow expand the macro while preserving the position of comments?

[albert-github]

An argument ends with the , so I thought maybe reorganizing the places of the , a little bit like:

/**
 * Second enum with values.
 */
ENUM(Values2
    , Value1_2 ///< First value.
    , Value2_2 ///< Second value.
);

might help but this gives the same results:

/**
 * Second enum with values.
 */

///< First value.
///< Second value.
 enum class  Values2  {  Value1_2, Value2_2  } ;

When using the /**< / */ type comments like:

/**
 * Third enum with values.
 */
ENUM(Values3
    , Value1_3 /**< First value. */
    , Value2_3 /**< Second value. */
);

we get

///< First value.
///< Second value.
 enum class  Values2  {  Value1_2, Value2_2  } ;
/**
 * Third enum with values.
 */



 enum class  Values3  {  Value1_3 /**< First value. */, Value2_3 /**< Second value. */  } ;

and the result is:

which looks OK to me (also the original formulation with /**< instead of ///< looks OK).

All in all there looks like to be a difference in handling /**< and ///< comments.

Example: example.tar.gz

As a side note "the latest master (1.12.0)" is a moving target better would be to specify the complete output of doxygen -v.
(I tried with 1.12.0 (38ee114))

[kanje]

Indeed, replacing ///< with /**< and */ works around the issue, also for 1.9.5. Thanks!

As a side note "the latest master (1.12.0)" is a moving target better would be to specify the complete output of doxygen -v.
(I tried with 1.12.0 (38ee114))

Point taken!

[doxygen]

@kanje Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official release becomes available.

[kanje]

@doxygen The problem is fixed, thanks!

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.12.0.
Please verify if this is indeed the case. Reopen the
issue 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).