-
Notifications
You must be signed in to change notification settings - Fork 630
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
Empty spaces in fortran lexer keyword recognition #1188
Labels
A-lexing
area: changes to individual lexers
changelog-update
Items which need to get mentioned in the changelog
S-minor
severity: minor
X-imported
imported from Bitbucket
Comments
Anteru
added
T-feature
type: a new feature
X-imported
imported from Bitbucket
S-minor
severity: minor
labels
Aug 31, 2019
Anteru
added
changelog-update
Items which need to get mentioned in the changelog
and removed
T-feature
type: a new feature
labels
Feb 12, 2021
This was referenced Mar 8, 2021
This was referenced Mar 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-lexing
area: changes to individual lexers
changelog-update
Items which need to get mentioned in the changelog
S-minor
severity: minor
X-imported
imported from Bitbucket
(Original issue 1484 created by anphi on 2018-11-14T20:37:47.258741+00:00)
Fortran allows arbitrary empty space to be embedded in keywords.
For example, it is legal to write "e n d d o"
While probably nobody would do this, and we don't want to request the lexer to handle that, some people run together certain multi-word keywords, such as "enddo" instead of "end do". The current Fortran lexer does not recognize such them. Could you please make any inter-word space for keywords optional, so that both versions are matched?
The text was updated successfully, but these errors were encountered: