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 617190 - Fortran comments with ^C and only one ' confuse doxygen
Fortran comments with ^C and only one ' confuse doxygen
Status: RESOLVED DUPLICATE of bug 625601
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-04-29 15:34 UTC by Jonas
Modified: 2012-11-18 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Parser error with state 20 (17.68 KB, application/zip)
2010-12-22 07:34 UTC, Jonas 		Details
Parser error with state 20 (D'ENTREE) (17.70 KB, application/zip)
2010-12-22 08:01 UTC, Jonas 		Details

Description Jonas 2010-04-29 15:34:53 UTC 
Comments like

CC    PARAMETRES D'ENTREE

confuse the parser. (searching the closing ')

!!    PARAMETRES D'ENTREE

is ok.
Comment 1 Jonas 2010-05-04 14:40:58 UTC 
I think there are more chars that not working with starting C comment style but with !! and this:

CHAR_ARRAY(I)='\'

is not working too. Looks like the single backslash is the suspect.

Best regards
Comment 2 Daniel Franke 2010-12-21 21:21:18 UTC 
(In reply to comment #0)
> Comments like
> 
> CC    PARAMETRES D'ENTREE
> 
> confuse the parser. (searching the closing ')

Could you please provide a fully self contained testcase and error messages, if any? I can not reproduce the problem.


(In reply to comment #1)
> CHAR_ARRAY(I)='\'
> is not working too. Looks like the single backslash is the suspect.

There are some other reports about this, e.g. #630580.
Comment 3 Jonas 2010-12-22 07:34:56 UTC 
Created attachment 176883 [details]
Parser error with state 20
Comment 4 Jonas 2010-12-22 08:01:18 UTC 
Created attachment 176885 [details]
Parser error with state 20 (D'ENTREE)
Comment 5 Jonas 2010-12-22 08:12:32 UTC 
If I run doxygen on all (really big) files I got a lot more error messages:

Error in file b1.f line: 2323, state: 20
Error in file b2.f line: 4206, state: 4
Error in file c1.f line: 11453, state: 4
parse error in end <scopename>
Error in file c12.f line: 10337, state: 6
Error in file c14.f line: 28712, state: 20
Error in file c18.f line: 7822, state: 20
Error in file c2b.f line: 21015, state: 20
parse error in end <scopename>
Error in file c36.f line: 10755, state: 6
Error in file c37.f line: 12535, state: 17
Error in file c5.f line: 15581, state: 17

every time the last line at file. (all tested with version 1.7.2)
Comment 6 Daniel Franke 2010-12-22 19:30:33 UTC 
The example has:

!!
CC  D'ENTREE
!!

In this case, the file is internally recognized as free form and thus only '!' are used as comment indicators. Hence, doxygen tries to interpret CC as statement and 'ENTREE as string. Using 'C' or '!' comments throughout does not show any problem.

The 'C' comment style is obsolescent, one shouldn't use it any more.

For doxygen, I see two things:
 (a) do not base fixed/free form recognition on this
 (b) allow either comment style for any source form

I'll close this as dupe as it an example of what #625601 is about.

The problem with '\' is already tracked elsewhere.

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