GNOME Bugzilla – Bug 721032
Trouble with /cond /endcond
Last modified: 2014-04-21 10:09:24 UTC
I have downloaded version 1.8.6 today. And used it for my project. When I have seen generated documentation - I seen that most of my classes missing in the list of classes. I began compare them with the few resting. I noticed the difference: hidden classes contents \cond \endcond block inside. I have deleted this block, after what the classes reappeared. I try use @cond @endcond - but result the same (no classes). I try use \@cond \@endcond - then classes reappeared.
\cond .. \endcond are made to hide stuff, so without example I cannot tell whether this a bug or desired behaviour. Can you please attach a (minimal) self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Created attachment 264872 [details] Classes A B C with block cond inside Archive conteins A, B C java example classes, Doxyfile of the project, and results of documentation creation with 1.8.5 and 1.8.6 version.
In all classes I try to hide function foo1 for documentation. For classes A and B it is work in version 1.8.5, but don't work in version 1.8.6. Class C incorrect - but it is correctly work for both version. It demonstrates only that without cond tag documentation generates.
Confirmed. This happens for languages that do not have a C-Preprocessor (e.g. java) and if you use /** @cond */. A workaround is to use /// @cond or /** @cond */ instead.
Hello, I try to use style (/// @cond) like you recomended. And old bug has been fixed. But I noticed a new one. Problem when I use two cond blocks in succession. After this before third function I see * or ** (depending on the syntax) near returned type. I add sample in additional files. In sample A **, in sample B *, in sample C without.
Created attachment 264924 [details] Sample A, B, C All classes have same text but different formating. And sample A and B return incorrect documentation for third function.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.7. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant (preferrably in the form of a self-contained example).