Re: [Doxygen-develop] [PATCH] Support for C++ comments next to arguments of macro function

[Albert <alb...@gm...>]

Dear Christian,

What happens in case of multi-line inline comments?
E.g.:
DECLARE_ENUM(Foo_t,
     foo1 = 0x000000001, ///< First comment.
                                    ///< continuation of first comment
     foo2 = 22, ///< Second comment.
                    ///< continuation of second comment
     foo3
 );

Best Regards,

Albert

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Dec 10, 2017 at 7:10 PM, Christian Schoenebeck via Doxygen-develop <
dox...@li...> wrote:

> Hi,
>
> please consider the attached patch for git, which allows code input like
> this
> to be processed correctly:
>
>  #ifndef DECLARE_ENUM
>  # define DECLARE_ENUM(type, ...) enum type { __VA_ARGS__ }
>  #endif
>
>  DECLARE_ENUM(Foo_t,
>      foo1 = 0x000000001, ///< First comment.
>      foo2 = 22, ///< Second comment.
>      foo3
>  );
>
> The current general behavior of dropping all new line characters on macro
> expansion is preserved. Accordingly those C++ comments are automatically
> rewritten as inline C comments instead.
>
> Best regards,
> Christian Schoenebeck
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>
>