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: problem with types with name starting with is (Origin: bugzilla #709845) #5313

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

On 2013-10-10 17:35:49 +0000, albert wrote:

In Fortran types with a name starting with is are not shown in the documentation as the they are considered as a "type is".

A small example showing the problem(used doxyfile is a standard file generated by doxygen -g):
!> \file
!> file documenation module_tst

  !> @brief documentation module tst
  module tst
    !> @brief the TYPE IsAProblem is not shown by doxygen 1.8.5
    TYPE IsAProblem
      INTEGER :: element !< element in type isAProblem
    end type

    !> @brief the TYPE NoProblem is shown by doxygen 1.8.5
    TYPE NoProblem
      INTEGER :: element !< element in type NoProblem
    end type
  end module

On 2013-10-10 17:43:47 +0000, albert wrote:

Submitted code to git, pull request 44

On 2013-10-11 17:40:11 +0000, Dimitri van Heesch wrote:

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

On 2013-12-24 18:59:21 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).

On 2013-12-29 17:18:32 +0000, albert wrote:

Verified, isaproblem is now seen so no problem anymore

@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