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: @var at the module level doesn't seem to work... (Origin: bugzilla #666008) #4499

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2011-12-12 16:00:17 +0000, Richard Munroe wrote:

I've tried the following in a wide variety of variants:

	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

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.


Dick Munroe

On 2013-04-14 18:21:34 +0000, albert wrote:

Created attachment 241514
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.

On 2013-05-10 14:32:21 +0000, Dimitri van Heesch wrote:

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

On 2013-05-19 12:36:23 +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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment