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 645423 - Fortran: Doxygen doesn't understand protected attribute
Fortran: Doxygen doesn't understand protected attribute
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.3
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-03-21 17:07 UTC by Marcus Mohr
Modified: 2013-01-20 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of html output (30.07 KB, image/png)
2011-03-21 17:07 UTC, Marcus Mohr
  Details
PATCH: enable Protected keyword (4.55 KB, patch)
2013-01-06 19:14 UTC, albert
none Details | Review

Description Marcus Mohr 2011-03-21 17:07:30 UTC
Created attachment 183966 [details]
Screenshot of html output

Fortran2003 introduced protected as attribute for module variables and pointers.
Doxygen fails to correctly recognise this attribute. In the following example

module readOnlyValues

  implicit none

  type :: readOnly
     integer :: valA
     integer :: valB
  end type readOnly

  type(readOnly), protected, save :: rom

end module readOnlyValues

it instead lists
- protected
- save
- rom
as variables of type(readOnly), see attached screen shot.

Cheers
Marcus
Comment 1 albert 2013-01-06 19:14:41 UTC
Created attachment 232872 [details] [review]
PATCH: enable Protected keyword

This patch enables the keyword protected, analogous to the keywords public and private.
Comment 2 Dimitri van Heesch 2013-01-15 20:16:27 UTC
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2013-01-20 13:35:02 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3.1. 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.