New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trouble with /cond /endcond (Origin: bugzilla #721032) #5387

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-12-25 10:16:19 +0000, Volodymyr wrote:

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.

On 2013-12-25 10:22:13 +0000, Dimitri van Heesch wrote:

\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?

On 2013-12-25 11:50:26 +0000, Volodymyr wrote:

Created attachment 264872
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.

On 2013-12-25 12:00:00 +0000, Volodymyr wrote:

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.

On 2013-12-25 12:28:34 +0000, Dimitri van Heesch wrote:

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.

On 2013-12-27 07:42:16 +0000, Volodymyr wrote:

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.

On 2013-12-27 07:44:56 +0000, Volodymyr wrote:

Created attachment 264924
Sample A, B, C

All classes have same text but different formating. And sample A and B return incorrect documentation for third function.

On 2014-04-21 10:09:24 +0000, Dimitri van Heesch wrote:

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

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment