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: In initialization statement the "=" (equal sign) is missing (Origin: bugzilla #682740) #4865

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-08-26 18:29:58 +0000, albert wrote:

In the Fortran documentation the "=" (equal sign)is missing in e.g. the save statement and the parameter statement.

Example:
module tst
integer, parameter :: par_f = 92 !< docu par_f
integer, save :: par_s = 93 !< docu par_s
end module

In the documentation we see:
integer, parameter par_f 92
integer, save par_s 93
and
integer, parameter tst::par_f 92
integer, save tst::par_s 93

instead of:
integer, parameter par_f = 92
integer, save par_s = 93
and
integer, parameter tst::par_f = 92
integer, save tst::par_s = 93

On 2012-08-26 18:32:55 +0000, albert wrote:

Created attachment 222490
PATCH: retain "=" in Fortran output

With this patch the "=" (equal sign) is retained in the output of the initialization.

On 2012-09-22 18:02:25 +0000, Dimitri van Heesch wrote:

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

On 2012-12-26 16:09:02 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3. 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 2013-01-05 12:58:02 +0000, albert wrote:

Patch is in and works

@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