albert-github

@doxygen I assume you saw the errors when building the doxygen documentation ...

I don't get the problem, when I have: ``` /// \file /// the documentation of the macro #define MACRO_1 42 #define MACRO_2 42 /// \var MACRO_2 /// \brief the documentation...

The `MACRO_EXPANSION` is about how the macros, from the code, will be represented in the resulting documentation. Can you give a, small, self contained example (source+configuration file in a, compressed,...

I don't think this is a problem in doxygen but a problem in your raw string there is a double quote (`"`) and this will terminate the raw string.I think...

> It's the sole point of raw strings to not have to escape things. > I strongly assume this is not about qregularexpression so just drop it an use a...

I had a solution for the initial example, but the example in https://github.com/doxygen/doxygen/issues/11166#issuecomment-2387977680 gave with that solutions some problems. Extended fix. I've just pushed a proposed patch, pull request #11167

Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release).

Best is not to refer to the stack overflow page but copy the text here (and also parts of the relevant comments), so when the stackoverflow question is removed for...

I looked in the code of the doxygen preprocessor and saw that there is a special rule for defines that are defined without arguments (the case with comment "// empty...

The "problem" occurs only occurs when you have what you called "include guard macros" so: ``` #ifndef HEADER_HPP #define HEADER_HPP ... the real content of the include file ... #endif...