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 654866 - Fortran function types with spaces result in error
Fortran function types with spaces result in error
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-07-18 18:38 UTC by albert
Modified: 2012-11-18 11:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for Fortran funcions with brackets and spaces in type (1.60 KB, patch)
2011-07-18 18:45 UTC, albert 		none Details | Review

Description albert 2011-07-18 18:38:29 UTC 
In case the return type of a function has brackets and a space between this bracket this leads to an error message.

The following example code:
MODULE mod_aa

CONTAINS
  FUNCTION StrUpCase ( Input_string ) RESULT ( Output_String )
    CHARACTER ( * ) :: Input_String
    CHARACTER ( LEN( Input_String ) ) :: Output_String
  END FUNCTION StrUpCase
END MODULE mod_aa

leads to the following message:

Searching for member function documentation...
D:/aa.f90:-1: warning: documented function `mod_aa::CHARACTER' was
 not declared or defined.


We get similar messages in case we use eg. type (typ )
Comment 1 albert 2011-07-18 18:45:31 UTC 
Created attachment 192212 [details] [review]
Patch for Fortran funcions with brackets and spaces in type

This patch skips in case of Fortran some checking for function pointers. It also has a comparison made cases insensitive (fortranscanner.l)
Comment 2 Dimitri van Heesch 2011-07-28 19:16:57 UTC 
Thanks, I'll include the patch in the next subversion update.
Comment 3 Dimitri van Heesch 2011-08-14 14:04:34 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. 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 2011-10-30 18:13:15 UTC 
No error message is produced anymore and results are OK.