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

Closing long comment line "/////////...." being included in @brief. (Origin: bugzilla #700345) #5171

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 normal in component general for ---
Reported in version 1.8.3.1-SVN on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-05-14 21:49:29 +0000, Timmie Smith wrote:

Created attachment 244248
Demonstrates issue with long comment line following single line @brief.

The format I'm using to document my code is

//////////////////////////////////////////////////////////////////////
/// @brief What does this method do?
/// @param What is the type, name, and meaning of this parameter?
/// @return What is the type, name, and meaning of the return value?
///
/// [optional details about how to use the method]
//////////////////////////////////////////////////////////////////////

In cases where there's only a single line brief the closing line of the block is being included in the @brief comment. This is occurring with a build from SVN, but does not occur when using 1.8.1 in Fedora 17.

Source file that demonstrates the error is attached. The only change to the default Doxyfile is setting INPUT = test.cc

On 2013-05-17 18:32:20 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-05-17 18:33:44 +0000, Dimitri van Heesch wrote:

Created attachment 244568
Proposed fix to ignore ////

Please check if this patch fixes the problem

On 2013-05-17 18:57:21 +0000, Timmie Smith wrote:

The patch fixes the issue for me. Thank you.

On 2013-05-19 12:36:06 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.

@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