https://bugs.winehq.org/show_bug.cgi?id=53644
--- Comment #4 from Robert Wilhelm sloper42@yahoo.com --- (In reply to Jason Millard from comment #3)
So maybe that was what the FIXME was about?
Thanks for testing my patch. The patch added two shift/reduce conflicts. vbscript allows some keywords like "property" to be used as an identifier. E.g. it is legal to write "Dim property". If I disallow tPROPERTY as identifier like below , I can parse your sample. This is of course not an acceptable solution.
@@ -498,7 +495,7 @@ Identifier | tDEFAULT { ctx->last_token = tIdentifier; $$ = $1; } | tERROR { ctx->last_token = tIdentifier; $$ = $1; } | tEXPLICIT { ctx->last_token = tIdentifier; $$ = $1; } - | tPROPERTY { ctx->last_token = tIdentifier; $$ = $1; } + /* | tPROPERTY { ctx->last_token = tIdentifier; $$ = $1; } */ | tSTEP { ctx->last_token = tIdentifier; $$ = $1; }