On Fri May 22 17:37:13 2026 +0000, Jacek Caban wrote:
I'm not sure about moving that logic to the compiler. Technically, this is the kind of thing the parser should handle. The statement separation syntax in vbscript is very nuanced, so I can see why it's tempting to move it into the compiler (that is also one of the reasons why I considered rewriting the parser in pure C at some point). I could be fine with that approach in some cases, but the additional state tracking needed to reconstruct parser state does not seem great. Note that the distinction between the parser and bytecode emitter stages is not purely internal. It has some externally visible effects. For example, with this MR, something like the following: ``` sub s() class c end class end sub ; parse error ; ``` would report a parser error in line 5 instead of failing earlier in line 2 first. (Admittedly, it's not a very important difference.) Another attempt
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10897#note_141066