#23 Dangling semi-colon on PUT # produces wrong error

Open
opened 2 years ago by ChipMaster · 0 comments

PUT with a semi-colon at the end of the command produces an “undefined variable” error. I spend too much time with languages that terminate all commands with semi-colons! I’m guessing that a trailing comma causes the same error. This should be reported as a “syntax error”... otherwise somebody is liable to rip their hair out trying to figure out what is wrong with their perfectly good variable.

Example command:

PUT #1, , s$;
`PUT` with a semi-colon at the end of the command produces an "undefined variable" error. I spend too much time with languages that terminate all commands with semi-colons! I'm guessing that a trailing comma causes the same error. This should be reported as a "syntax error"... otherwise somebody is liable to rip their hair out trying to figure out what is wrong with their perfectly good variable. Example command: ``` PUT #1, , s$; ```
ChipMaster added the
blunder
label 2 years ago
ChipMaster changed title from Dangling semi-colon on PUT # errors with "undefined variable" to Dangling semi-colon on PUT # produces wrong error 2 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.