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 function types with spaces result in error (Origin: bugzilla #654866) #4340

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 unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-07-18 18:38:29 +0000, albert wrote:

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👎 warning: documented function `mod_aa::CHARACTER' was
not declared or defined.

We get similar messages in case we use eg. type (typ )

On 2011-07-18 18:45:31 +0000, albert wrote:

Created attachment 192212
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)

On 2011-07-28 19:16:57 +0000, Dimitri van Heesch wrote:

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

On 2011-08-14 14:04:34 +0000, Dimitri van Heesch wrote:

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.

On 2011-10-30 18:13:15 +0000, albert wrote:

No error message is produced anymore and results are OK.

@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