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 694027 - Fortran: derive intent from documentation in case no intent is specified
Fortran: derive intent from documentation in case no intent is specified
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.3.1-SVN
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-02-17 14:38 UTC by albert
Modified: 2013-05-21 15:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
PATCH get intent from documentation (3.35 KB, patch)
2013-02-17 14:42 UTC, albert
none Details | Review

Description albert 2013-02-17 14:38:22 UTC
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.

Example:

subroutine a(x)
  integer :: x !< [in] description of x
end subroutine
Comment 1 albert 2013-02-17 14:42:33 UTC
Created attachment 236451 [details] [review]
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.
Comment 2 Dimitri van Heesch 2013-03-31 12:44:26 UTC
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2013-05-19 12:35:51 UTC
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.
Comment 4 albert 2013-05-21 15:50:13 UTC
Works as expected