You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current state is better than before the fix for #20, but ~ now seems to be treated as an operator like +, etc but really it's more like ' as it can't be used in most expressions. I think it only works in PRINT and as the next token after STR$ (so A$=STR$~(12) and B$=STR$~12 work, but C$=STR$(~12) doesn't.)
Admittedly a minor issue, but ideally A=~B should show ~ in red.
The text was updated successfully, but these errors were encountered:
# is only valid right after certain tokens - BGET#, BPUT#, CLOSE#, EOF#, EXT#, INPUT#, PRINT#, PTR#,
I've pushed a fix for # handling so it's now coloured as a syntax error in places where it isn't valid.
We don't currently take account of the more restricted syntax of INPUT# and PRINT# but we don't try to handle the exact syntax of most BASIC commands either. Also INPUT# and PRINT# are relatively obscure and aren't likely to be useful with the bot because there's no disk or tape to read from/write to.
Following on from #20...
The current state is better than before the fix for #20, but
~
now seems to be treated as an operator like+
, etc but really it's more like'
as it can't be used in most expressions. I think it only works inPRINT
and as the next token afterSTR$
(soA$=STR$~(12)
andB$=STR$~12
work, butC$=STR$(~12)
doesn't.)Admittedly a minor issue, but ideally
A=~B
should show~
in red.The text was updated successfully, but these errors were encountered: