I have found that the following program behaves differently in GWBASIC and PC-BASIC 15.08.3:
10 ON ERROR GOTO 30
20 ERROR
30 ON ERROR GOTO 30:RESUME 40
40 PRINT "END"
In GW-BASIC, the program will run without interruption and displays "END" on the screen. On the other hand, the program will display "RESUME without error in 30" when running in PC-BASIC 15.08.3. I would consider it a bug of PC-BASIC in this case.
Also I have a suggestion regarding the settings in the PC-BASIC configuration file (PCBASIC.INI). It seems that certain contents will be considered comments by PC-BASIC if and only if the symbol "#" is in the beginning of a line currently. Lines such as "pen=left # choices: left, middle, right, none" will trigger warnings or errors since in such cases the remarks following "#" are considered part of the directives by PC-BASIC which are however not recognized. This makes it more difficult for people who try to uncomment some directives by simply removing the first "#" symbol from original lines such as "# pen=left # choices: left, middle, right, none". Furthermore, in the case of "# copy-paste=left, middle # choices: left, middle, right, none", it is even slightly more complicated, since I have found that PC-BASIC will strictly only recognize "copy-paste=left,middle", not "copy-paste=left, middle" (with a white space before "middle" as in the original line), nor "copy-paste=left,middle # choices: left, middle, right, none" (with original remarks following the actual directive). Hope it will be made more flexible. Thanks!
Tested in Windows 10 x64.
Wengier
Last edit: Wengier 2016-01-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Wengier, thanks for reporting - I agree that's a bug, will be fixed for the .4 release.
The file format of the config file is defined by the ConfigParser module, which is part of the Python standard library. It seems that indeed inline comments can't start with a hash and rather need a semicolon. I'll fix the config file so that it is more usable.
I'll have a look into spaces in lists - again of course the examples ought to be correct, so will remove spaces from any lists and malke clear in the comments that there should be no spaces around the commas in lists.
Thanks for pointing out the issues, indeed the example config file needs some attention.
Rob
Last edit: Rob Hagemans 2016-01-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have found that the following program behaves differently in GWBASIC and PC-BASIC 15.08.3:
10 ON ERROR GOTO 30
20 ERROR
30 ON ERROR GOTO 30:RESUME 40
40 PRINT "END"
In GW-BASIC, the program will run without interruption and displays "END" on the screen. On the other hand, the program will display "RESUME without error in 30" when running in PC-BASIC 15.08.3. I would consider it a bug of PC-BASIC in this case.
Also I have a suggestion regarding the settings in the PC-BASIC configuration file (PCBASIC.INI). It seems that certain contents will be considered comments by PC-BASIC if and only if the symbol "#" is in the beginning of a line currently. Lines such as "pen=left # choices: left, middle, right, none" will trigger warnings or errors since in such cases the remarks following "#" are considered part of the directives by PC-BASIC which are however not recognized. This makes it more difficult for people who try to uncomment some directives by simply removing the first "#" symbol from original lines such as "# pen=left # choices: left, middle, right, none". Furthermore, in the case of "# copy-paste=left, middle # choices: left, middle, right, none", it is even slightly more complicated, since I have found that PC-BASIC will strictly only recognize "copy-paste=left,middle", not "copy-paste=left, middle" (with a white space before "middle" as in the original line), nor "copy-paste=left,middle # choices: left, middle, right, none" (with original remarks following the actual directive). Hope it will be made more flexible. Thanks!
Tested in Windows 10 x64.
Wengier
Last edit: Wengier 2016-01-18
Hi Wengier, thanks for reporting - I agree that's a bug, will be fixed for the .4 release.
The file format of the config file is defined by the ConfigParser module, which is part of the Python standard library. It seems that indeed inline comments can't start with a hash and rather need a semicolon. I'll fix the config file so that it is more usable.
I'll have a look into spaces in lists - again of course the examples ought to be correct, so will remove spaces from any lists and malke clear in the comments that there should be no spaces around the commas in lists.
Thanks for pointing out the issues, indeed the example config file needs some attention.
Rob
Last edit: Rob Hagemans 2016-01-18