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 682740 - Fortran: In initialization statement the "=" (equal sign) is missing
Fortran: In initialization statement the "=" (equal sign) is missing
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.1.2-SVN
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-08-26 18:29 UTC by albert
Modified: 2013-01-05 12:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
PATCH: retain "=" in Fortran output (761 bytes, patch)
2012-08-26 18:32 UTC, albert
none Details | Review

Description albert 2012-08-26 18:29:58 UTC
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
Comment 1 albert 2012-08-26 18:32:55 UTC
Created attachment 222490 [details] [review]
PATCH: retain "=" in Fortran output

With this patch the "=" (equal sign) is retained in the output of the initialization.
Comment 2 Dimitri van Heesch 2012-09-22 18:02:25 UTC
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2012-12-26 16:09:02 UTC
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.
Comment 4 albert 2013-01-05 12:58:02 UTC
Patch is in and works