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

Fortran: comma at begin of argument list description in case of implicit type (Origin: bugzilla #680398) #4814

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component general for ---
Reported in version 1.8.1.2-SVN on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-07-22 11:39:39 +0000, albert wrote:

In case an argument of a Fortran routine has no type (e.g. it is implicitly typed) but has an other attribute then the first character in the documentation is a ','

Example program:

Subroutine test(a, b, c)
external a
dimension(5) b
dimension(15) c
logical c
end subroutine

Example output:

subroutine test (, external a,
, dimension(5) b,
logical, dimension(15) c
)

Correct output:

subroutine test (external a,
dimension(5) b,
logical, dimension(15) c
)

On 2012-07-22 11:43:11 +0000, albert wrote:

Created attachment 219412
PATCH: remove unwanted comma in argument list

This patch removes an unwanted comma at the beginning of the argument description

On 2012-07-28 19:15:45 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2012-08-11 13:18:28 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.2. 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.

On 2012-08-12 12:28:48 +0000, albert wrote:

Works as described

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment