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
changed title from Dangling semi-colon on PUT # errors with "undefined variable" to Dangling semi-colon on PUT # produces wrong error3 years ago
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:
Dangling semi-colon on PUT # errors with "undefined variable"to Dangling semi-colon on PUT # produces wrong error 3 years ago