GNOME Bugzilla – Bug 652869
JavaDoc style stopped working for F77 code
Last modified: 2014-01-01 18:34:20 UTC
Been using JavaDoc style in F77 code for many years. recently updated to 1.7.4 and found it does not work. Narrowed it down to last working in 1.7.2 SUBROUTINE SIMPLE_TEST(I,X,CSTRING) * /** @file simple_test.for * @brief SIMPLE_TEST(I,X,CSTRING) * <p> * simple_test of f77 code with doxygen * * works in 1.7.2 * * stopped working in 1.7.3 * </p> * @param INTEGER*4 I * @param REAL*8 X * @param CHARACTER*(*) CSTRING * */ IMPLICIT NONE INTEGER*4 I REAL*8 X CHARACTER*(*) CSTRING RETURN END
I never saw this construct before. I tried to reproduce the behavior as described with the 1.7.2 version but was not able to do it, must have to do something with the used Doxyfile. Can you provide the used Doxyfile?
Created attachment 264913 [details] doxygen 1.7.2 run folder
Created attachment 264914 [details] doxygen 1.8.6 run folder
I've attached two files which have the Doxygen file and output
Can you provide me the input and output that worked with the 1.7.2 version. I tried this input and output with the 1.7.2 version and got no output either.
It was in the doxygen_1_7_2_run.tar.gz is there a problem with the attachment?
There is no problem with the attachment, I just missed it Sorry. I'll have a look into the problem as soon as possible.
Created attachment 265104 [details] Example in new style The functionality didn't disappear but the way of the .for extension is handled by default changed between the versions 1.7.2 and 1.7.3 see: Bug 637712 - Fortran: support .for extension. To the best of my knowledge till version 1.7.2 files with extension .for were handled as C-like files, as of version 1.7.3 they are handled as real Fortran files. To obtain again the old "functionality" specify with EXTENSION_MAPPING for=C. The big disadvantage is that one does not use the checking mechanisms of doxygen (used parameters, source browsing, linking of functions etc.). It looked like documentation but was far off from the capabilities of doxygen. Please compare the output generated with the current version of doxygen with the attached file and the original documentation. I think this is not a bug.
This bug appears to be a duplicate per comment #8, so I am closing this bug as a duplicate. *** This bug has been marked as a duplicate of bug 637712 ***