Closed Tailzer closed 4 years ago
The syntax validation isn't 100% complete implementation of NextBASIC's parser (mostly because the parser - as far as I know - is closed source), so it's mostly used as a helper.
Where I find there should be an error and my validation didn't pick it up, I'll normally try to adjust my logic for that use case - so your example code is perfect and can help me improve the tool for others too.
I've found most of the recent validation bugs have been around print statements and what's allowed with semi-colon separation and what's not.
I'll file as a bug and get a fix in.
ok cool, that makes sense. If i spot anything else ill shout. Thanks
Fixed in the latest release: 1.5.4 - thanks again.
Not sure if this is a bug or feature request? or out of scope?
I made a typo and the extension didn't pick it up?
code example: 330 PRINT INK 2; AT 19,12; CHR$ 147; CHR$ 145; CHR$ 147; PAUSE 6
returns a C Nonsense in Basic error due to the ';' preceding the PAUSE as it is expecting a ':'