New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested Aliases fail when the nested alias has two or more arguments. (Origin: bugzilla #711378) #5340

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2013-11-04 07:16:14 +0000, Tom Ghyselinck wrote:

Created attachment 258903
Issue with nested ALIASES

Hi,

In bug report 704172 ( https://bugzilla.gnome.org/show_bug.cgi?id=704172 ),
this issue has been set as resolved, but in our documentation, it still
poses issues.

We are currently using the latest release 1.8.5 of doxygen for TCL and C/C++.

This issue still seems to be happening:

  • when defining:

    ALIASES += apitest{2}="ARG0: \1 ARG1: \2"

  • with he following code documentation

    /**

    • \mainpage
    • \apitest{A, B \apitest{C, D}}
      */

This ends up in

ARG0: A ARG1: B {C, D}

I tried various combinations of escaping '{', ',' and '}'
Always leading to similar output.

Can you verify this, it is getting a very urgent issue for us.

I attached a very basic test source.
( Doxyfile was generated with 'doxygen -g', I only changed the 'ALIASES' )

Thank you very much in advance!

On 2013-12-07 22:18:56 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-09 08:01:07 +0000, Tom Ghyselinck wrote:

Thank you very much for the update!

I verified the fix, also with "multi-layer" nesting.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment