AF5NE

After recompiling the following test should confirm the second bug is fixed. bwBASIC: REM TEST 'RUN' COMMAND bwBASIC: bwBASIC: bwBASIC: LIST 100 PRINT "HELLO" bwBASIC: SAVE "GOOD.BAS" bwBASIC: bwBASIC: bwBASIC: REM THESE SHOULD DISPLAY "HELLO" bwBASIC: bwBASIC: bwBASIC: RUN HELLO bwBASIC: RUN 100 HELLO bwBASIC: RUN#100 HELLO bwBASIC: RUN "GOOD.BAS" HELLO bwBASIC: bwBASIC: bwBASIC: REM THESE SHOULD DISPLAY AN ERROR MESSAGE bwBASIC: bwBASIC: bwBASIC: RUN 1 ERROR: Undefined line bwBASIC: RUN 999 ERROR:...

Glad the initial bug is fixed. The attached "patch-20230419.txt" should fix the second bug you reported above.

Thanks for finding this bug. Sorry for the delay in responding - I am not often online. If you are comfortable updating the source code with diff/patch, the attached "patch-20230417.txt" should fix this bug and all the other bugs I know about. If you are not comfortable with diff/patch, then open "bwb_cmd.c" with a text editor and goto to around line 1555, which should look like this: if (line_read_expression (L, X) == FALSE) /* bwb_run_filename_or_linenumber */ { WARN_SYNTAX_ERROR; return L; } Update...

My apologies for the late response -- I am not often online. If you would be so kind, please try this: gcc -D_SVID_SOURCE -o bwbasic -lm bw*.c

My apologies for the late response -- I'm not often online. Please remove the trailing semicolon. OLD: while (line_skip_seperator (l)); NEW: while (line_skip_seperator (l))

Daniel, My apologies for the late response -- I am not often online. If you would be so kind, please try this: gcc -D_SVID_SOURCE -o bwbasic -lm bw*.c

Ken, My apologies for the late reply, I am rarely online. Please use the "shell" command with version 3.20. For example: 100 rem list the current directory 110 shell "ls" 999 end

Ken, First: Yes, the change was intentional. Previously, the following typo would erase the entire directory: rm *** rm The following does something rm *** when what was intended was rem *** rem The following does something rem *** Notice the missing letter 'e'. By requiring the "shell" keyword, the prior will cause an error instead of erasing all file (including the program which contained the typo). I did it myself and that is why I changed it. Second: I'm not the author of the batch files you...