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
...which obviously (and undesirably) has different behaviour from the original program!
I wonder if basictool could check for this buggy ENDPROC-concatenation issue and spit out a warning if it occurs? Maybe basictool could internally generate the ASCII listing for the code, post-Packing, and search each line for ENDPROC followed by optional spaces, a colon, and more code on the same line? (Or maybe it would be easier to search the tokenised form of the program instead -- but I didn't want to suggest that because of the risk of finding false positives..?)
(What's weird is that I didn't run into this problem until recently, when I added PROCa at the start of G.HAMP01 (click "Display"): http://bbcmicro.co.uk/explore.php?id=3199 Till then, there were seemingly dozens of PROCs (scroll down that page) which PRES ABE Pack concatenated correctly, without any issues! Obviously I must have hit a particular set of circumstances that triggered the bug with PROCa. (My workaround, btw, is to add a colon followed by an asterisk after the ENDPROC of PROCa! That prevents PRES ABE Pack from trying to concatenate it.))
The text was updated successfully, but these errors were encountered:
I seem to have found an unfortunate bug in PRES ABE Pack, which hence also affects basictool.
If you say Yes to all the Pack options (including Concatenate) and pack the following program...
...then PRES ABE Pack will turn it into this...
10DEFPROCa:PRINT"In PROCa":ENDPROC:PROCa:PRINT"Outside PROCa"
...which obviously (and undesirably) has different behaviour from the original program!
I wonder if basictool could check for this buggy ENDPROC-concatenation issue and spit out a warning if it occurs? Maybe basictool could internally generate the ASCII listing for the code, post-Packing, and search each line for ENDPROC followed by optional spaces, a colon, and more code on the same line? (Or maybe it would be easier to search the tokenised form of the program instead -- but I didn't want to suggest that because of the risk of finding false positives..?)
(What's weird is that I didn't run into this problem until recently, when I added PROCa at the start of G.HAMP01 (click "Display"): http://bbcmicro.co.uk/explore.php?id=3199 Till then, there were seemingly dozens of PROCs (scroll down that page) which PRES ABE Pack concatenated correctly, without any issues! Obviously I must have hit a particular set of circumstances that triggered the bug with PROCa. (My workaround, btw, is to add a colon followed by an asterisk after the ENDPROC of PROCa! That prevents PRES ABE Pack from trying to concatenate it.))
The text was updated successfully, but these errors were encountered: