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: in body documentation lands on wrong place (Origin: bugzilla #706520) #5270

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

Original attachment names and IDs:

On 2013-08-21 17:38:34 +0000, albert wrote:

Created attachment 252633
Source files and Doxyfile to reproduce bug

In case in Fortran in body docs are used they land not with the current routine, but with the next routine (and in case of the last routine of a file they are lost).
When using C the the in body docs are shown with the right routine.

The attachment contains a Fortran source file showing the problem (as well as a small reference C file and the used configuration file).

On 2013-08-21 17:51:49 +0000, albert wrote:

Resolution has been pushed to git repository and a pull request has been
emitted.

On 2013-08-22 10:13:13 +0000, Dimitri van Heesch wrote:

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

On 2013-08-23 15:04:41 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.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 2013-08-23 17:19:57 +0000, albert wrote:

In body docs are now at the place I expect them to be

On 2013-09-02 16:38:28 +0000, albert wrote:

In some cases, in propriety code, with in body Fortran documentation doxygen crashed.
A bugfix has been committed to github.

On 2013-12-24 18:59:44 +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 18:17:14 +0000, albert wrote:

In 1.8.6 crash is not present 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