GNOME Bugzilla – Bug 796621
@cond does not stop at @endcond Fortran
Last modified: 2018-07-30 10:58:48 UTC
!<@cond scan function ModelPath(AuxString, Level) ... end function ModelPath !<@endcond produces error: Conditional section with label scan does not have a corresponding \endcond command within this file. (warning treated as error, aborting now) *** Doxygen has finished Have tried variations of the syntax to no avail. inside the function is a fortran intrinsic 'scan' that Doxygen can't handle and simply exits when reached during parsing.
I tried to reproduce the problem, but didn't succeed. Can you please attach a, small, self contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
Created attachment 372721 [details] Self-contained test So, the problem is more complex in behavior than I previously exposed. In the example you can see two uses of 'scan' in the same function. If the second use, inside the conditional statement, is commented out Doxy runs and @cond works as expected I believe. Otherwise the error occurs.
The problem here is that doxygen has some problems with the backslash in Fortran. When I use a backslash I use the parameter: CHARACTER(LEN=1), PARAMETER :: backSlash = char(92) !< the back slash (\\) character and concatenate this into the string.
(In reply to albert from comment #3) > The problem here is that doxygen has some problems with the backslash in > Fortran. > > When I use a backslash I use the parameter: > CHARACTER(LEN=1), PARAMETER :: backSlash = char(92) !< the back slash (\\) > character > > and concatenate this into the string. Thank you very much. Can you think of any other way to force the doxygen parser to simply not read the '\'? I'm not at the liberty to change the source at this moment...
No I didn't find a solution, therefore I used the parameter as indicated.
Thank you!
Looks like I found a workaround, don't use " (double quotes) but ' (single quotes)
The previous comment was not completely correct but a bit luck (due to the ' in doesn't. I checked the code and I've just pushed a proposed patch to github (pull request 773, https://github.com/doxygen/doxygen/pull/773).
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to https://github.com/doxygen/doxygen/issues All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github. Hence I am closing this GNOME Bugzilla ticket. Please use the corresponding ticket in Github instead. Thanks a lot!