Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parser misinterpreting fortran (Origin: bugzilla #733705) #5525

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.8.7 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-07-25 00:54:33 +0000, mike wrote:

Created attachment 281650
doxygen configuration file

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

  subroutine sub2

  subroutine sub3

On 2014-07-25 16:46:43 +0000, albert wrote:

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.

On 2014-07-27 09:18:27 +0000, albert wrote:

Comment from submitter:
In short, the 1.8.7 version didn't produce the good behavior for me but the 1.6.1 did.

On 2017-08-23 17:33:02 +0000, albert wrote:

I just pushed a proposed patch to github (pull request 592)

On 2017-09-02 16:19:44 +0000, albert wrote:

update has been integrated into the main version on github

On 2017-12-25 18:43:53 +0000, Dimitri van Heesch wrote:

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).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.