diff options
| -rw-r--r-- | unprotbas.1 | 5 | ||||
| -rw-r--r-- | unprotbas.rst | 5 |
2 files changed, 6 insertions, 4 deletions
diff --git a/unprotbas.1 b/unprotbas.1 index e3bdee4..1e1b919 100644 --- a/unprotbas.1 +++ b/unprotbas.1 @@ -205,8 +205,9 @@ use the RUN command with a filename, and if the program ever exits will get stuck again. .sp This doesn\(aqt \fIhave\fP to be done with the last line in the program, -though it normally is. The "poisoned" line could be followed by more -lines of code, though they could never actually execute. +though it normally is. The "poisoned" line can never be executed (or +BASIC will lock up), but it could be followed by more lines of code +(which also could never be executed). .sp Line 32100 in the example above does this job, taking advantage of the STMCUR pointer used by BASIC, which holds the address of the diff --git a/unprotbas.rst b/unprotbas.rst index 3143baf..cf7ca84 100644 --- a/unprotbas.rst +++ b/unprotbas.rst @@ -179,8 +179,9 @@ Bad next-line pointer will get stuck again. This doesn't *have* to be done with the last line in the program, - though it normally is. The "poisoned" line could be followed by more - lines of code, though they could never actually execute. + though it normally is. The "poisoned" line can never be executed (or + BASIC will lock up), but it could be followed by more lines of code + (which also could never be executed). Line 32100 in the example above does this job, taking advantage of the STMCUR pointer used by BASIC, which holds the address of the |