albert-github

Probably you can create the required files. When building you use normally just by giving the command `make`. To run the xml tests one can give the command `make tests`and...

@doxygen I don't think this is correct as now the tests are always performed against the xsd even when this is not requested, e.g. ``` make tests TEST_FLAGS="--xhtml --id 1...

The idea that came into my mind was to use an extra `sed` step and replacing all `>` by `>\n` in the tests. As we use `diff -b -w ...`...

I've just pushed a proposed patch, pull request #11864 @pgajdos Please verify if the referenced proposed pull request fixes the problem for you.

@pgajdos In the doxygen 1.15.0 a workaround was introduced, but when you would use with the doxygen version 1.15.0: `doxygen tests TEST_FLAGS="--xml --xmlxsd"` I think the problem for test 9...

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).

Unfortunately the image does not belong to the given example. When running the example I get: we indeed see here indeed a fgunction `Seq(char)` this is because the macro /...

> because defining a function like Seq(char) CharSeq is invalid since C99. doxygen requires a valid (compiling) program, when the code doesn't adhere to this anything can happen.

It is valid code when the `MACRO_EXPANSION = YES` otherwise it is invalid (in doxygen's view)

In the second example we see that in the file `config.h` we have (at the end): ``` #include "config_rules.h" ``` and in the file `config_rules.h` we have: ``` #include "SIMRCV.h"...