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 625602 - FORTRAN: comment in subroutine argument list
FORTRAN: comment in subroutine argument list
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-07-29 17:28 UTC by albert
Modified: 2016-09-07 09:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Source code (198 bytes, application/octet-stream)
2010-07-29 17:28 UTC, albert 		Details
HTML output (4.21 KB, text/plain)
2010-07-29 17:29 UTC, albert 		Details

Description albert 2010-07-29 17:28:28 UTC 
Created attachment 166786 [details]
Source code

In case one specifies comments or empty lines between the arguments of a subroutine (on seperate lines) this comment should be skipped but it is not. It is handled in a strange was (see attachements with source code and html output).

Example code:
      subroutine sub(

     1  x)
        integer x
      end
      subroutine sub1(
C comment
     1  x)
        integer x
      end
Comment 1 albert 2010-07-29 17:29:11 UTC 
Created attachment 166787 [details]
HTML output
Comment 2 albert 2015-01-06 13:48:21 UTC 
This is a similar situation as with bug_742452, the handling of empty lines and comment lines in case of continuation lines. bug_742745 is addressing free formatted code, and this is fixed formatted code. Solution will be similar.
Comment 3 albert 2016-08-27 16:12:36 UTC 
I've just pushed a proposed patch to github (pull request 508)
Comment 4 albert 2016-08-28 16:12:47 UTC 
Code has been integrated in the master branch on github.
Comment 5 Dimitri van Heesch 2016-09-05 13:46:43 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).