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

Fortran: resulting HTML based on FORTRAN 90 code contains */ in output for first routine and variable/parameter (Origin: bugzilla #615507) #3731

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2010-04-12 10:09:54 +0000, wrote:

Created attachment 158466
Zip file with project,code,output and screenshot.

Dear developer,

Since a while I am using Doxygen with great pleasure to generate developer and user documentation (HTML/CHM/LATEX) based on the same Fortran 90 source code :-).

In the resulting documentation, I find an have an annoying */ in my HTML and LATEX output. I cannot remove it and it appears to surface only at the first routine and parameter/variable being commented with Doxygen.

I am running Doxygen on Windows XP 32 bit professional

The source code is Fortran 90.

Used the following Doxygen binary:

I have attached the project file, the Fortran 90 source code, a screen-shot and the resulting HTML and LATEX code.

Thanks for your time,

Marco van Goethem

On 2010-12-23 20:18:53 +0000, Daniel Franke wrote:

Confirmed. Reduced testcase:

-- 8< --
!> @endcond
-- 8< --

for this, the scanner reads:

Reading /home/daniel/pr/pr615507/fortran-bug.f90...
Parsing file /home/daniel/pr/pr615507/fortran-bug.f90...
--(end of buffer or a NUL)
--accepting rule at line 277 ("!> */
--accepting rule at line 786 ("!>")
--accepting rule at line 797 (" */")

This is strange as there obviously is no "*/" in the code above. It was silently inserted somewhere, probably by the handling of @cond?!

Dimitri, I think this is one is for you.

On 2011-01-01 19:17:32 +0000, Dimitri van Heesch wrote:

This is indeed caused by the @cond, @endcond handling in commentcnv.l (which is a preprocessing step run before parsing).

I'll make this part more Fortran aware.

On 2011-01-03 19:01:35 +0000, Dimitri van Heesch wrote:

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