fparser
fparser copied to clipboard
stfc
This project maintains and develops a Fortran parser called fparser2 written purely in Python which supports Fortran 2003 and some Fortran 2008. A legacy parser fparser1 is also available but is not s...
It would be useful if we could capture the line numbers from the original code in the parse tree. This is available in the reader so should be able to...
As evidenced in test_readfortran.py, test_f2py_directive_f77, f2py directives are not correctly handled in Fortran77 source (they seem to be entirely discarded by the reader).
Rule 913 has a *lot* of constraints, the majority of which fparser does not attempt to enforce. These are documented in the docstring of the class `Io_Control_Spec_List`.
In #252 it was discovered that the array-constructor matching is questionable. Although some tests were added there, full testing is still not performed. In particular, constraint C497 is not obeyed...
Sorry, another archaic one... Matching of Hollerith constants seems to have a few issues. I noticed the following: 1. In a Format string, if the last item before the closing...
The rule in the F2003 standard is ``` (R440) data-component-def-stmt is declaration-type-spec [ [ , component-attr-spec-list ] :: ] component-decl -list ``` The relevant class is `Data_Component_Def_Stmt` and was subclassed...
In #249 some attributes were added to the F2008 support. However, a large number of constraints is currently not checked in both 2003 and 2008 parser. As suggested in https://github.com/stfc/fparser/pull/249#pullrequestreview-375628013...
In #249 some attributes were added to the F2008 support. However, a large number of constraints is currently not checked in both 2003 and 2008 parser. As suggested in https://github.com/stfc/fparser/pull/249#pullrequestreview-375628013...
This is born out of #239. Fortran is case-insensitive but some situations require case-sensitive matching (for example preprocessor directives). For such cases it would be desirable to have a case-sensitive...