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
In fparser2, the implementation of f2003 rule 835 <nonblock-do-stmt> = <action-term-do-construct>|<outer-shared-do-construct> checks for action-term-do-construct first and this appears to return a valid tree even if there are nested loops.
The obvious solution would be to re-order the order of rule checking. However, the implementation of outer-shared-do-construct and inner-shared-do-construct do not restore the reader if they fail to match, which will cause parse failures, so this also needs fixing at the same time.
When this is fixed then f2008 do concurrent support for these two classes should also be added.
The text was updated successfully, but these errors were encountered:
In fparser2, the implementation of f2003 rule 835
<nonblock-do-stmt> = <action-term-do-construct>|<outer-shared-do-construct>
checks foraction-term-do-construct
first and this appears to return a valid tree even if there are nested loops.The obvious solution would be to re-order the order of rule checking. However, the implementation of
outer-shared-do-construct
andinner-shared-do-construct
do not restore the reader if they fail to match, which will cause parse failures, so this also needs fixing at the same time.When this is fixed then f2008 do concurrent support for these two classes should also be added.
The text was updated successfully, but these errors were encountered: