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 639954 - Fortran array constructors with brackets not correctly recognized.
Fortran array constructors with brackets not correctly recognized.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.2
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 695274 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-19 15:04 UTC by Thomas
Modified: 2013-05-19 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example configuration file (6.19 KB, application/octet-stream)
2011-01-19 15:04 UTC, Thomas 		  Details
PATCH: Enable Fortran 2003 initializations (1.12 KB, patch)
2013-02-16 15:30 UTC, albert 		none Details | Review

Description Thomas 2011-01-19 15:04:54 UTC 
Created attachment 178730 [details]
Example configuration file

The following Fortran 2003-conforming code with bracket array constructors:
===
module testdoc
    integer, dimension(3) :: a = (/ 1, 2, 3 /)
    integer, dimension(3) :: b = [ 4, 5, 6 ]
end module testdoc
===

results in truncated HTML documentation:
===
testdoc Module Reference
Variables
integer, dimension(3) 	a = (/ 1, 2, 3 /)
integer, dimension(3) 	b = [ 4
Variable Documentation
integer,dimension(3) testdoc::a = (/ 1, 2, 3 /)
integer,dimension(3) testdoc::b = [ 4
===
Comment 1 albert 2013-02-16 15:30:10 UTC 
Created attachment 236370 [details] [review]
PATCH: Enable Fortran 2003 initializations

With this patch besides the pre 2003 initialization possibilities (/ ... /) also the possibility  [ ... ] is enables.

Note: We expect to have valid Fortran code so (/ ... ] and [ ... /) are not seen as errors.
Comment 2 Dimitri van Heesch 2013-02-23 10:09:56 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 3 albert 2013-03-06 17:25:44 UTC 
*** Bug 695274 has been marked as a duplicate of this bug. ***
Comment 4 dummfikk 2013-03-06 18:22:48 UTC 
sorry for the duplicated bug report, it's the first time I'm using such a system

Thanks for the patch (and of course for Doxygen in general)
Comment 5 Dimitri van Heesch 2013-05-19 12:35:39 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.