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 666008 - Fortran: @var at the module level doesn't seem to work...
Fortran: @var at the module level doesn't seem to work...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.5.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-12-12 16:00 UTC by Richard Munroe
Modified: 2013-05-19 12:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
PATCH: Correcting behavior for @var in case of Fortran (541 bytes, patch)
2013-04-14 18:21 UTC, albert 		none Details | Review

Description Richard Munroe 2011-12-12 16:00:17 UTC 
I've tried the following in a wide variety of variants:
<pre>
	MODULE socialSecurity

        ...

	!++
	!> @var socialSecurity::defaultDateOfEntitlement
	!> The first of the month in which retirement insurance benefits could be paid
	!> in full.  It is the first full month following the default full retirement
	!> age.
	!--
	
	TYPE(t_date)::					defaultDateOfEntitlement( 
	1										parameterHusbandIndex:parameterWifeIndex)

	END MODULE socialSecurity
</pre>

and cannot get any documentation of the variable defaultDateOfEntitlement in the Doxygen output.

I've tried:

1. Leaving off the variable name.

2. Leaving of the module name.

3. Attaching the documentation block to the variable declaration itself.

All with no joy.

It would really be nice to be able to document module level state for Fortran code.

Best,

Dick Munroe
Comment 1 albert 2013-04-14 18:21:34 UTC 
Created attachment 241514 [details] [review]
PATCH: Correcting behavior for @var in case of Fortran

The name of the @var (@fn etc.) was derived by means of the function parsePrototype. For Fortran this routine was empty, placed the name of the element (text) supplied in the current entity.
Comment 2 Dimitri van Heesch 2013-05-10 14:32:21 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2013-05-19 12:36:23 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.