Fixed a bug where specifications were being misinterpreted inside IFs during parsing

I find it surprising this bug had been in there so long. It was interpreting "INT i" as an expression in an IF, then couldn't resolve i, rather than backing out and correctly parsing the whole line, "INT i:" as a specification.
2009-04-12 16:26:54 +00:00 · 2009-04-12 16:26:54 +00:00 · 80dac0492b
commit 80dac0492b
parent 8f943c9ac1
1 changed files with 1 additions and 2 deletions
--- a/frontends/ParseOccam.hs
+++ b/frontends/ParseOccam.hs
@ -1741,8 +1741,7 @@ ifChoice
 guardedChoice :: OccParser (A.Structured A.Choice)
 guardedChoice
    =   do m <- md
-           b <- expression
-           eol
+           b <- tryVX expression eol
           indent
           p <- process
           outdent