GNOME Bugzilla – Bug 628417
Fortran: doxygen filter, preparsing fixed form of null
Last modified: 2012-02-27 07:17:04 UTC
Created attachment 169162 [details] Files needed to reproduce the problem Dear doxygen, I have writen a doxygen filter which helps to interpret fortran like code. If I only transmit the code unchanged to doxygen I get the following error message: Preparsing fixed form of null With the attached code you can reproduce the problem. best regards, Julika Burger
Dear Julika, I've run this problem as well and had no real problems. I only got the following: parse error in end <scopename>************************************************** ****************** Error in file D:/doxygen_bugs/bug_628017/gen2.f line: 8, state: 6 ******************************************************************** This is due to the fact that the indentation is not correct for a fixed format Fortran file (the word SUBROUTINE only has 5 spaces instead of the required 6). Can you confirm this ? When confirmed maybe you can set set this bug to resolved and subsequently to verified ? best regards, Albert
Please set this bug to resolved, as no reaction from Julika has been received
Resolved as requested.
With doxygen 1.6.3 I still have this problem. It will take some time to verify it with doxygen 1.7.X I am working on a diskless client with a common image for all client terminals and the update of new software is notr so easy.
With doxygen 1.7.5.1 I still get an error message: Preparsing fixed form of <filename> I am now working under SuSe 11 with gfortran 4.3.62.198. I have attached my fortran file and a doxygen.cfg file.
Created attachment 206497 [details] Current Testcase
Created attachment 206542 [details] [review] PATCH message now printed through msg instead of printf The message was printed by means of printf and not through the routine msg. This is fixed in this patch. In QUIET mode this resulted in the fact that the message was printed, now it is not printed in QUIET mode anymore.
Thanks, I'll include the patch in the next release.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.0. 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.
It will take some time to install the doxygen version in our system, I verify it as soon as possible. thanks for your help and best regards