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: derive intent from documentation in case no intent is specified (Origin: bugzilla #694027) #5079

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2013-02-17 14:38:22 +0000, albert wrote:

In case the documentation of an argument directly in front or after it and the user has not specified the intent attribute but placed the [i], [out] or [in,out] at the begin of the documentation this is not seen as intent description.


subroutine a(x)
integer :: x !< [in] description of x
end subroutine

On 2013-02-17 14:42:33 +0000, albert wrote:

Created attachment 236451
PATCH get intent from documentation

Check whether or not the intent value is given at the begin of the documentation. When this is the case compare this intent with the specified intent.
In case no intent is given use the intent from the documentation.
In case of a discrepancy between the documentation and the documentation issue a warning.

On 2013-03-31 12:44:26 +0000, Dimitri van Heesch wrote:

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

On 2013-05-19 12:35:51 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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 2013-05-21 15:50:13 +0000, albert wrote:

Works as expected

@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