Syntax highlighting fails at inline forall statements #169
Comments
|
Thank you for the report and Fix :+1 |
pedro-ricardo
added a commit
that referenced
this issue
May 15, 2020
### Check List - Highlight - [x] `select` keyword - *Merge #165 to fix #149* - [x] `rank` keyword - *Merge #165* - [x] `forall` keyword - *Merge #170 to fix #169* - Symbol List - [x] Symbols bug in VSCode +1.40 - *Merge #161 to fix #154* - [x] Symbols classification - *Merge #141 to fix #140* - [x] Long named symbols - *Merge #151* - Settings - [x] Add more options - *Merge #152* - Dependencies - [x] Merge `dependabot` PR's - [x] lodash - *Merge #144* - [x] mixin-deep - *Merge #146* - [x] handlebars - *Merge #155* - Code Completion - [x] Array constructor - *Fix #148* - New Features - [x] Breakpoints - *Merge #150*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all - nice extension, thanks for your work in maintaining this repo.
The syntax highlighting appears to be incorrect for
forallstatements that consist of only one line. Please see the following example:In line 4,
arr(i) = i * ihas been highlighted in red, even though this is valid syntax and the file compiles (gfortran). The error propagates to other parts of the program too: notice that theendstatement is also no longer highlighted here. For comparison, compare with the highlighting when theforallremoved.In more complex files, this error propagation becomes quite severe, causing a large number of syntax-highlighting issues, rendering some files almost unreadable.
Many thanks.
The text was updated successfully, but these errors were encountered: