Dimitri van Heesch

This issue was previously marked 'fixed but not released', which means it should be fixed in doxygen version 1.14.0. Please verify if this is indeed the case. Reopen the issue...

@mutalibmohammed No, see my remark in #11704 why it is not easy to create an official binary for a platform I do not own myself (short summary: no static version...

> Question is what happens in this case when one has a class with a number of functions ... Indeed, if I remember correctly, I made something like the above...

@albert-github This makes it work for `\if` but not for `\cond`. I think it would be better to do the `\doxyconfig` handling inside the `CondParser`.

@JonathanBittner 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.

From Doxygen's point of view, the `using Foo::Bar;` statement brings a 'copy' of the Bar class into the scope of the `foo.cpp` file. This is different from `using namespace Foo;`...

@oxidase The problem with providing official binaries is that they are build against a statically build version of libclang to improve portability. This is a rather tricky and lengthy process,...

@oxidase Sound like good approach. As mentioned, first something needs to be done to get a static build of libclang. [This project](https://github.com/deech/libclang-static-build) used to be good for this but has...

@dropbearrob Nice work. I need to chew on it a bit, but I think this is something that can be merged in.

@dropbearrob Can you attach an example project that shows the use of `REQUIREMENTS_FILES` and `REQUIREMENTS_TAGFILES` in combination with the `\verifies` and `\satisfies` commands? It is not entirely clear to me...