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 #704172) #5239

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

On 2013-07-13 20:58:11 +0000, Mark Cianciosa wrote:

When attempting to nest one alias with multiple arguments inside a second alias with multiple arguments, doxygen miss counts the number of arguments in the outer alias.

The following example shows this behavior.

/** @mainpage

Produced with config

ALIASES = alias1{3}="\section \1, \2\n

ALIASES += alias2{2}="\1\2"

See Also:

On 2013-08-03 17:41:24 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-08-23 15:04:29 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. 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.

On 2013-10-28 07:25:28 +0000, Tom Ghyselinck wrote:

Hi, I am 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"

The following code

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

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.

@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