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 array constructors with brackets not correctly recognized. (Origin: bugzilla #639954) #4096

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2011-01-19 15:04:54 +0000, Thomas wrote:

Created attachment 178730
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

On 2013-02-16 15:30:10 +0000, albert wrote:

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

On 2013-02-23 10:09:56 +0000, Dimitri van Heesch wrote:

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

On 2013-03-06 17:25:44 +0000, albert wrote:

*** Bug 695274 has been marked as a duplicate of this bug. ***

On 2013-03-06 18:22:48 +0000, dummfikk@gmx.de wrote:

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)

On 2013-05-19 12:35:39 +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