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 653356 - doxygen fails to produce output depending on blanks in Fortran code
doxygen fails to produce output depending on blanks in Fortran code
Status: RESOLVED DUPLICATE of bug 625601
Product: doxygen
Classification: Other
Component: general
unspecified
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-06-24 17:35 UTC by alan.a.wray
Modified: 2012-11-18 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description alan.a.wray 2011-06-24 17:35:48 UTC 
The following piece of Fortran is processed correctly by doxygen:

!> Compute atomic bound-bound transitions

     Subroutine atom_bb

     End Subroutine atom_bb

Whereas the following rather similar code (one more blank!) does not:

!> Compute atomic bound-bound transitions

      Subroutine atom_bb

     End Subroutine atom_bb


The "File Reference" section is empty in the latter case.
Comment 1 albert 2011-07-03 19:31:36 UTC 
Dear Alan,

I had a look at your problem.

Can you confirm that in the second example the number of spaces before the "End" are 5 ?
Can you confirm that you also get the error message like:
********************************************************************
Error in file .../aa.f90 line: 8, state: 4
********************************************************************

If this is the case, the problem is in the determination whether the code is fixed or free formatted code. In the latter case the checker for free / formatted code thinks it is fixed formatted code.
There is already a bug report on the free / fixed formatted issue.

Best Regards,

Albert
Comment 2 Dimitri van Heesch 2011-07-17 13:02:43 UTC 
On request of Albert I made this a duplicate of bug 625601.

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