Add support for parsing "floating" code#25
Merged
Conversation
alvrogd
commented
Jan 28, 2026
alvrogd
force-pushed
the
feature/ParseFloatingCode
branch
from
9464798 to
6f3d78c
Compare
alvrogd
requested review from
a team,
d-alonso and
jgonzac
and removed request for
a team
inaki-amatria
approved these changes
Jan 28, 2026
alvrogd
force-pushed
the
feature/ParseFloatingCode
branch
from
6f3d78c to
348768f
Compare
It seems that there was a slip in the previous merge point, and the test was left as is in upstream, without applying to the expected output the modifications from the patches in this fork.
alvrogd
force-pushed
the
feature/ParseFloatingCode
branch
from
348768f to
169c985
Compare
The goal is to allow specification parts and executable statements at top-level, in addition to the usually allowed Fortran items. This is particularly useful for parsing include files, which typically contain fragments of code rather than complete Fortran translation units. Incomplete blocks of code, such as partial derived type declarations or do loops, will still trigger parsing errors.
alvrogd
force-pushed
the
feature/ParseFloatingCode
branch
from
169c985 to
d0c100a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the grammar to allow specification parts and executable statements at top-level, in addition to the usually allowed Fortran items. This is particularly useful for parsing include files, which typically contain fragments of code rather than complete Fortran translation units.
Note: I've tested the updated grammar in the SIESTA project. No parsing regressions were introduced.