After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630580 - FORTRAN: Doxygen output not correct with '\' character in Fortran code
FORTRAN: Doxygen output not correct with '\' character in Fortran code
Status: RESOLVED DUPLICATE of bug 596872
Product: doxygen
Classification: Other
Component: general
1.7.1-SVN
Other All
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 616364 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-09-25 17:02 UTC by pavanakumar
Modified: 2010-12-24 12:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description pavanakumar 2010-09-25 17:02:31 UTC
Doxygen does not correctly parse the '\' character in FORTRAN code. For example, the Doxygen html output of the source code displays incorrect line numbers and colouring.

IF ( c(i:i).EQ.'/' .OR. c(i:i).EQ.'\' ) THEN
 Dir_Len = i
END IF 

I actually could fix this problem by doing this

CHARACTER BKSLASH*2
BKSLASH='\\'
IF ( c(i:i).EQ.'/' .OR. c(i:i).EQ.BKSLASH(1:1) ) THEN
 Dir_Len = i
END IF

I think this is due to the fact that Doxygen was desigend to parse C/C++ programs, where the '\' character is used as a escape sequence. But in F77/F90 this is not the case. But hats off to the folks for adding FORTRAN support to Doxygen. You have done a great work.

Cheers,

Pavanakumar Mohanamuraly
Comment 1 albert 2010-11-06 14:19:59 UTC
Another solution for this problem is:
CHARACTER(LEN=1), PARAMETER :: backSlash = char(92)

(this problem has also been reported as bug 616364)
Comment 2 Dimitri van Heesch 2010-11-06 17:46:15 UTC
*** Bug 616364 has been marked as a duplicate of this bug. ***
Comment 3 Daniel Franke 2010-12-13 22:52:05 UTC
Related (if not dupe of one of) #596872 and/or #602952.
Comment 4 Daniel Franke 2010-12-24 12:38:31 UTC

*** This bug has been marked as a duplicate of bug 596872 ***