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 643219 - Fortran: parsing semicolon
Fortran: parsing semicolon
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.3-SVN
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-02-24 19:31 UTC by albert
Modified: 2011-10-30 19:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for fortran semicolon problem (1.03 KB, patch)
2011-02-24 20:05 UTC, albert
none Details | Review

Description albert 2011-02-24 19:31:21 UTC
When a statement contains a semicolon (;) as separator between statements the second statement is not handled properly. This is especially noticeable in case the statement is the end program statement. Doxygen emits an error.

Example:
program main
   call abort();end program main


Preprocessing C:/Users/user/AppData/Local/Temp/tst/semicolon_bug.f90...
Parsing file C:/Users/user/AppData/Local/Temp/tst/semicolon_bug.f90...
********************************************************************
Error in file C:/Users/user/AppData/Local/Temp/tst/semicolon_bug.f90 line: 4, state: 10
********************************************************************

This bug is related to bug 521854 wheer a similar problem was found and fixed for variables.
Comment 1 albert 2011-02-24 20:05:57 UTC
Created attachment 181867 [details] [review]
Patch for fortran semicolon problem

This patch detects a semicolon and ignores it in case it is in a string or in comment or otherwise it will start processing similar to the case that a new line was started.
Comment 2 Dimitri van Heesch 2011-05-15 09:58:07 UTC
Thanks Albert,

I'll include this patch in the next subversion update.
Comment 3 Dimitri van Heesch 2011-08-14 14:04:55 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. 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.
Comment 4 albert 2011-10-30 19:39:37 UTC
No error anymore