remy / vscode-nextbasic

VS Code tools for NextBASIC
https://marketplace.visualstudio.com/items?itemName=remysharp.nextbasic
8 stars 2 forks source link

BANK %27 DPOKE %y<<1,%BANK 27 DPEEK (319-n<<1) #61

Closed NealeTools closed 1 month ago

NealeTools commented 2 months ago

v1.11.7 BANK %27 DPOKE %y<<1,%BANK 27 DPEEK (319-n<<1) Also encodes incorrectly (but fine once re-entered in ZXOS 2.08).

(Error seems to be caused by the "%" after the comma (but this is essential because the whole part is an integer expression.)

NealeTools commented 1 month ago

Hi Remy, Just wondering if these issues are still on your radar for a fix? Thanks!

remy commented 1 month ago

On my radar, just need to carve the time.

On Sat, 1 Jun 2024, 19:51 MattN, @.***> wrote:

Hi Remy, Just wondering if these issues are still on your radar for a fix? Thanks!

— Reply to this email directly, view it on GitHub https://github.com/remy/vscode-nextbasic/issues/61#issuecomment-2143547834, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADLBCIVTVOBSF72MTP7LLZFIJ3LAVCNFSM6AAAAABHAA7L5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGU2DOOBTGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

remy commented 1 month ago

Just for me, it's this part that's bad: %BANK 27 DPEEK (319-n<<1) - the statement is an integer expression, but once in the parens, the number is treated as literal (instead of int) - which causes the parse error.

remy commented 1 month ago

vscode extension 1.11.8 has all these fixes. Very wary I've refactored the int logic, but there's over 200 tests, so I'm hoping there's on regressions.

NealeTools commented 1 month ago

Thanks. Testing...