-
Notifications
You must be signed in to change notification settings - Fork 65
Improve parsing of Fortran array specifications #687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@gold2718 Is this still a work in progress? I see that the CI is not passing. |
…e_errors Merge up to head of develop to ensure tests still pass
|
@mkavulich, sorry about that, I had forgotten about this. It turns out that a last piece of the development was never committed and uploaded. I did that and also merged up to develop to make sure this is (I hope) ready to go now. |
climbfuji
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks very much for fixing this!
|
@mkavulich, is this ready to move forward? |
Improve parsing of Fortran array specifications
capgen was reporting odd errors when a semi-colon typo appeared in the middle of an
array specification.
This is due to the fact that the semi-colon is a Fortran special character used to separate statements making it possible to have multiple statements on a single source line.
This PR allows semi-colons to appear in parentheses in a statement.
To have this result in a more useful parsing error, some refactoring was done on how the Fortran parser collects and displays errors (an onion peel I have wanted to do for a while although there is plenty of onion left).
User interface changes?: No
Fixes: #362
Testing:
test removed:
unit tests:
system tests:
manual testing: