Export fails due to parsing bugs (examples in thread): about vscode-nextbasic HOT 17 CLOSED

yep - you can disable it from the settings ("Perform custom inline NextBASIC validation" - uncheck that)

from vscode-nextbasic.

Found the code now, it says the default is false, but somehow I changed the default much deeper down to true 🤦

from vscode-nextbasic.

Okay, v1.11.1 (all the ones) disables validation during export. Sorry that took so long.

from vscode-nextbasic.

Note to self: I need to merge the logic from the parser across to the validation (specifically subStatement int logic)

from vscode-nextbasic.

Bump: example 2 and 3 still fail export in v1.11.8

from vscode-nextbasic.

Yeah, this is validation, as per my comment, I need to make time to merge the logic from the new parsing to the validator (not a simple process)

from vscode-nextbasic.

In the short-term could you just turn off the validator? The code compiles and runs fine in CSpect, so the tokenisation is OK, but export never happens due to the check, so I cannot test any export functionality etc. :-)

from vscode-nextbasic.

Great! My apologies for not realising what this option did! 🫣

from vscode-nextbasic.

Hi @remy : Unfortunately, unticking this option does not allow the export to complete. I can see that the red underline no longer is present, but the file does not build if there are any syntax errors. This prevents me exporting to test on HW via NextSync, which is an essential part of my workflow now because I am using some HW features that CSpect does not support - thanks!

from vscode-nextbasic.

from vscode-nextbasic.

@remy Apologies for the nag, but is there any quick fix for turning off the validation on export? I feel like the new parser is 99% there! :-)
The validation check is currently preventing me from exporting working code as multiple .bank sections—or indeed exporting any code for test on HW. Thanks!

from vscode-nextbasic.

I'm snagging early morning time to get these done.

Any chance you have a snippet of the code that's causing this. I'm reviewing the code and it "says" it's not validating by default, so I wonder if I'm missing something else...

from vscode-nextbasic.

IF %SPRITE AT (j,1)>127 THEN SPRITE CONTINUE %j,,%SPRITE AT (j,1)-(i*i[0]) TO %239 STEP %SGN{-i[0]} RUN

from vscode-nextbasic.

Also %CODE and ERROR$ get underlined.
They pass "run in CSpect", so get encoded correctly, but the syntax checker flags them (red underline) and stops the Export script.

from vscode-nextbasic.

Actually, %CODE seems OK now, but ERROR$ is underlined and fails:

from vscode-nextbasic.

Here is the another one:

from vscode-nextbasic.

Thanks Remy! I can confirm the export now works (syntax is still underlined in red when enabled).

I'll try out bank exports next and hopefully there won't be any further headaches I unearth! :-)

from vscode-nextbasic.