albert-github

That is indeed the case I created a "proof of concept" working for the `\if` command and thought about adding it somewhere else in a generic way as well. I...

Unfortunately you didn't show the used settings (especially in this case `EXTRACT_STATIC`) seen the time elpased time since this issue was solved: please create a new issue with the following...

@cppljevans I see in the file html when running doxygen 1.14.0 I see: - where / what do you miss in respect to the alignas?

With the current doxygen version 1.15.0 I see in the brief description: So no mentioning of `T` or `alignas`. In the detailed description (using `ALWAYS_DETAILED_SEC = YES`) I see: So...

- I assume the output shown is from the simplified version. - I see only once the `id32` in the first output snippet (from xml/namespace_urho3_d.xml) so this looks OK for...

@doxygen in scanner.l in the rule `";"` I see: ``` yyextra->previous->type = "typedef "+yyextra->previous->args; ``` I don't think this is correct, it does not solve the underlying problem that looks...

@doxygen Did some tests and it looks like that as a `using` part is set to a `VARIABLE_SEC` in scanner.l (rule: `";"`) we get into the construction: ``` else if...

With doxygen 1.9.5 I see: ``` using Urho3D::color32 = typedef unsigned typedef unsigned Urho3D::id32 ``` in the xml file with the current doxygen version I see: ``` using Urho3D::color32 =...

With doxygen 1.9.6 we saw: with doxygen 1.15.0 we see: The change might be due to the switch from the `tabu` package to the `tabularray` package (#11634). So I think...

In the example we see: ``` /* The /*!< string inside a multiline comment prevents `PACK()` macro expansion. */ ``` This means that we have here a nested comment and...