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

Fortran: Wrong type of argument in case of out of place !< comment (Origin: bugzilla #676981) #4720

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

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-05-28 17:29:05 +0000, albert wrote:

In case of an out of place comment of type !< and the fact that the name van an argument is inside the documentation of this out of place comment, the argument takes the type of the variable to which the out of place comment belongs.

Example:

SUBROUTINE A(ff)
double precision :: ff
integer :: q !< ff

END SUBROUTINE

results in the detailed description section in:
subroutine a(integer ff)
instead of
subroutine a(double precision ff)

On 2012-05-28 17:35:48 +0000, albert wrote:

Created attachment 215138
Patch: Ignore out of place comment

THis patch sees to it that the out of place comment !< is ignored and the arguments have their correct type.

On 2012-06-17 17:23:37 +0000, Dimitri van Heesch wrote:

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

On 2012-07-12 15:41:52 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1.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-07-22 11:12:38 +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
You can’t perform that action at this time.