GNOME Bugzilla – Bug 521861
Fortran: Not recognized continuation character in fixed format code
Last modified: 2011-11-01 10:43:48 UTC
Please describe the problem: In fixed formatted code not all characters in column 6 are recognized as continuation characters. Example: MODULE tst REAL, DIMENSION(10) x :: tst1 REAL, DIMENSION(10) x :: tst2 END MODULE tst result: g.f:1: Warning: documented function `REAL tst::dimension' was not declared or defined. Steps to reproduce: 1. See description above Actual results: See description above Expected results: tst1 and tst2 are 2 local variables Does this happen every time? Yes Other information:
*** This bug has been marked as a duplicate of 534785 ***
Although it is set as a duplicate of 534785 this bug is still present in the current 1.5.7.1 SVN version (I cannot reopen bug 534785)
The above mentioned case is a problem of recognizing free versus fixed format code. Due to the space on position 7 in the first line the file is seen as free formatted code. Removing the space fixes this problem. The problem still exists in case a C, c or * is used as continuation character (allowed by the standard). A zero (0) is not allowed as continuation character. Example: module qq REAL c tst2 REAL ! tst3 REAL 0 tst4 end module qq
Created attachment 181872 [details] Fixing problem with continuation characters in fixed source form Fixing problem with continuation characters in fixed source form
Thanks, I'll include this patch in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.4. 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.
Seems I did not include the patch after all.
Should be corrected in the next subversion update.
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.
Te problem as described in this bug is fixed.