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 733705 - parser misinterpreting fortran
parser misinterpreting fortran
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7
Other Linux
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-07-25 00:54 UTC by mike
Modified: 2017-12-25 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
doxygen configuration file (10.54 KB, application/octet-stream)
2014-07-25 00:54 UTC, mike 		Details

Description mike 2014-07-25 00:54:33 UTC 
Created attachment 281650 [details]
doxygen configuration file

Hi,
I am building a call tree with doxygen and it thinks a variable is actually a function. This variable name is also a subroutine name so it mistakenly includes this subroutine in the call tree. The following piece of code reproduces the bug. Here the variable sub2 is defined as a logical and is used in sub1 in an if test. If the variable sub2 is defined in the first case (! bad), then sub1 points to sub2 in the call tree. If it is defined as in the second case, it doesn't point to sub2 in the call tree. Thanks

      subroutine sub1

      logical lbool,        ! bad
     &        sub2
!     logical lbool,sub2    ! good

      if(sub2) then
       call sub3
      endif
      return
      end

      subroutine sub2
      return
      end

      subroutine sub3
      return
      end
Comment 1 albert 2014-07-25 16:46:43 UTC 
I cannot reproduce the good behavior. can you attach a bad.f and a good.f to this bug report. The fact that in the bad case the sub2 is shown is not good. I'd like to be able to reproduce the good case as wll as it probably will make it easier to solve the problem.
Comment 2 albert 2014-07-27 09:18:27 UTC 
Comment from submitter:
In short, the 1.8.7 version didn't produce the good behavior for me but the 1.6.1 did.
Comment 3 albert 2017-08-23 17:33:02 UTC 
I just pushed a proposed patch to github (pull request 592)
Comment 4 albert 2017-09-02 16:19:44 UTC 
update has been integrated into the main version on github
Comment 5 Dimitri van Heesch 2017-12-25 18:43:53 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.14. 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).