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: Entities on line with USE, ONLY not hyper linked in code (Origin: bugzilla #680405) #4815

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

Original attachment names and IDs:

On 2012-07-22 17:50:43 +0000, albert wrote:

The entities on the same line as the USE, ONLY statement were not hyper linked in the code view, following items were.


!> \addtogroup mod1_grp desc
!> {
!> \name mod desc
!> {

  INTEGER, PARAMETER :: var2 = 2
  CHARACTER(len=4), PARAMETER    :: var1 = "1"

!> }
!> }


 USE mod1,  ONLY : var2    &
                     , var2    &
                     , var1


of mod2.f90 in the code the first var2 was not hyper linked whilst the second var2 and var1 were hyper linked (used here twice var2 for the demonstration purpose only)

On 2012-07-22 17:55:44 +0000, albert wrote:

Created attachment 219436
PATCH: hyperlink all entities with USE, ONLY

The attached patch hyper links also the items on the same line as USE, ONLY

On 2012-07-28 19:17:08 +0000, Dimitri van Heesch wrote:

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

On 2012-08-11 13:18:20 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.2. 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 2012-08-12 12:32:48 +0000, albert wrote:

Works as described

@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