Closed GoogleCodeExporter closed 9 years ago
The problem is that your fixed format fortran code has lines starting with #.
Afaik, this is not allowed by Fortran standard. However, it seems
reasonable to interpret such lines as comments (plus giving a warning).
I have applied the corresponding patch to fparser svn, now
the xxx.F is parsed successfully.
I think using .o extension for Fortran files is (highly) non-standard and
it does not make sense to support .o extensions by fparser. I would
reserve .o extensions for object files.
However, you can either rename such files or read these to
Python and feed their Fortran codes as strings to fparser.
Original comment by pearu.peterson
on 3 Mar 2010 at 2:10
Original comment by pearu.peterson
on 7 Mar 2010 at 11:18
Original issue reported on code.google.com by
TakaoKot...@gmail.com
on 3 Mar 2010 at 1:02Attachments: