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 707685 - Fortran: error message when missing last EOL
Fortran: error message when missing last EOL
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 709548 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-09-07 13:57 UTC by albert
Modified: 2013-12-29 17:27 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
File with sources showing the EOL Problem (261 bytes, application/x-taz)
2013-09-07 13:57 UTC, albert 		Details

Description albert 2013-09-07 13:57:42 UTC 
Created attachment 254346 [details]
File with sources showing the EOL Problem

When using the standard Doxyfile in version 1.8.5 (fee and fixed format) Fortran files with missing EOL with the last line will give an error message like:

********************************************************************
Error in file .../qq_fix.f line: 2, state: 4
********************************************************************
********************************************************************
Error in file .../qq_free.f90 line: 2, state: 4
********************************************************************

In the attached file there are the following files:
qq1_fix.f fixed source form with EOL with last line
qq_fix.f fixed source form without EOL with last line
qq1_free.f free source form with EOL with last line
qq_free.f free source form without EOL with last line
Comment 1 albert 2013-09-07 14:09:03 UTC 
I've pushed my solution to github
Comment 2 Dimitri van Heesch 2013-09-07 17:19:05 UTC 
Thanks, I'll include the patch in the next GIT update.
Comment 3 albert 2013-10-09 18:37:53 UTC 
*** Bug 709548 has been marked as a duplicate of this bug. ***
Comment 4 Dimitri van Heesch 2013-12-24 18:59:35 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).
Comment 5 albert 2013-12-29 17:27:20 UTC 
In version 1.8.6 error message is gone.