Dimitri van Heesch

@albert-github I restructured the code a bit (see [this commit](https://github.com/doxygen/doxygen/commit/589554349c563b34812b52cb1ecb165df7a352d9)) such that existing function `stripEmptyLines()` could be reused. Let me know if I overlooked something.

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

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

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

@albert-github You are right indeed. This was already wrong in 1.10.0 however, but should be fixed now.

@albert-github The 'problem' is that `@interface X(Y)` is an extension of `@interface X`, so a user would still refer to a method `init` added by extension `X(Y)` as `X::init` and...

Maybe a simpler solution is to distinguish between function like macros and plain macros and treat function like macros always as multiline, e.g. given ```C++ #define PI 3.14152965 #define MAX(x,y)...

@duncan-roe @albert-github I've implemented the alternative solution. Do not close the issue, this will be done automatically when the next official release becomes available.

@albert-github > I'm not really liking the distinction between the normal macro and the (small) function macro: This is of course a matter of taste. You could have the same...

@duncan-roe Sorry for reacting late, but I'm not really sure which problem you are addressing. Is this for C code? An inline function in C++ does not need to be...