Closed bradunov closed 9 years ago
I'm currently making a lot of changes to the parser so I suggest we wait until I commit this before fixing it.
Sure, no rush, I just want to make note of all the bugs/issues to have a comprehensive list here (though many parser ones will likely become obsolete after your modifications).
I believe this is fixed with parsec update, right?
The test
fun comp f() {
if(true);
return 0;
}
now gives
unexpected symbol ";"
expecting operator or "then"
and similarly for the expression language, so I am closing this issue as resolved for now.
A forgotten then in if-then-else results in error: unexpected "\n" instead of expecting then (which I believe used to be the case).