You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I was testing the OpenACC directive support I discovered that the OpenMP continuation (and thus the OpenACC continuation) does not highlight properly if the optional & appears on the continued line's sentinel. I tried to debug this myself as a part of the PR, but even with a few sets of eyes on it I wasn't able to get it working.
!$omp parallel &
!$&omp do
For the above code, if either & is left off the do will appropriately highlight, but if both are in place it does not. The specification allows for the ampersand on the sentinel and this is how I've seen it used in every code I've encountered.
The text was updated successfully, but these errors were encountered:
I think the solution to that might be similar (or hopefully identical to #203).
If that is the case and you decide to fix it yourself would you mind to mention #203 in the commit message so this code duplication is somewhat traceable in the git logs?
We really ought to find a better way to implement the syntax highlighting
While I was testing the OpenACC directive support I discovered that the OpenMP continuation (and thus the OpenACC continuation) does not highlight properly if the optional
&
appears on the continued line's sentinel. I tried to debug this myself as a part of the PR, but even with a few sets of eyes on it I wasn't able to get it working.For the above code, if either
&
is left off thedo
will appropriately highlight, but if both are in place it does not. The specification allows for the ampersand on the sentinel and this is how I've seen it used in every code I've encountered.The text was updated successfully, but these errors were encountered: