Re: [Doxygen-users] Problem documenting Fortran include file
Brought to you by:
dimitri
From: Albert <alb...@gm...> - 2013-10-10 18:15:40
|
Dear Joerg, Biking home I got an idea: why not use doxygen filter pattern capabilities? Did a small test with a python script: import sys import os f = open(sys.argv[1],'r') sys.stdout.write(" module __anonymous_%s__\n"%os.path.splitext(os.path.basename(sys.argv[1].replace("\\","/")))[0]) sys.stdout.write(f.read()) sys.stdout.write(" end module\n") wrapped it in a batch file and ran it. In my opinion good results. Albert On Thu, Oct 10, 2013 at 3:07 PM, Jörg Sichermann <Joe...@fg... > wrote: > Dear Albert,**** > > ** ** > > thank you very much for your answer. I suppsed something like that, but I > was unsure. At the moment I am documenting very old (form 1980 and older) > Fortran code using Doxygen an because of this the issue is still relevant > for me, too.**** > > ** ** > > Have a nice day,**** > > Joerg**** > > ___________________________________**** > > ** ** > > This e-mail and any attachments may contain confidential and/or privileged > material; it is for the intended addressee(s) only. If you are not a named > addressee, you must not use, retain or disclose such information.**** > > ** ** > > *Von:* Albert [mailto:alb...@gm...] > *Gesendet:* Donnerstag, 10. Oktober 2013 14:57 > *An:* Jörg Sichermann > *Cc:* dox...@li... > *Betreff:* Re: [Doxygen-users] Problem documenting Fortran include file*** > * > > ** ** > > Dear Joerg,**** > > A bit of an old message , had to dig for the original mail, but it is > still relevant.**** > > The problem here is that there is no begin (SUBROUTINE, FUNCTION, MODULE, > PROGRAM) and end statement it is, mot of the times, just a bunch of > declarations. The inc files are coming from the older Fortran versions > where there were no modules available. **** > > By chance I had a small thought about it. For Programs (the main program > is possible without program statement, the end statement though is > mandatory) I implemented a while ago that in case the program statement is > missing I create a dummy program statement with a name like (by > head)__<file_name>__**** > > For include files, well actually for files without begin and end statement > I was thinking about something similar, defining a module with name > __anonymous_<file_name>__**** > > problem is that one only knows if it was an include file when the entire > file has been read.**** > > This problem is on my list, with a lot of other Fortran / doxygen problems. > **** > > Albert**** > > ** ** > > On Thu, Oct 10, 2013 at 12:13 PM, Jörg Sichermann < > joe...@fg...> wrote:**** > > Dear Albert, > > I see the same error running Doxygen 1.8.5 > I saw the date of our message ( year 2010 ) - Does exist a solution now? > > Best Regards, > Joerg > > > > -- > View this message in context: > http://doxygen.10944.n7.nabble.com/Problem-documenting-Fortran-include-file-tp3694p6325.html > Sent from the Doxygen - Users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users**** > > ** ** > |