diff options
| author | B. Watson <urchlay@slackware.uk> | 2024-05-24 15:38:55 -0400 |
|---|---|---|
| committer | B. Watson <urchlay@slackware.uk> | 2024-05-24 15:38:55 -0400 |
| commit | 7421e70053b25a8609f2414dc595692afcd6b525 (patch) | |
| tree | ed935722ffb5d05fabdffec654493ce7c6722b28 /unprotbas.rst | |
| parent | 70299a6c57e6eaf95f15543e5c360de05aa64b62 (diff) | |
| download | bw-atari8-tools-7421e70053b25a8609f2414dc595692afcd6b525.tar.gz | |
unprotbas: tweak doc.
Diffstat (limited to 'unprotbas.rst')
| -rw-r--r-- | unprotbas.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/unprotbas.rst b/unprotbas.rst index 13c16a6..f6e733d 100644 --- a/unprotbas.rst +++ b/unprotbas.rst @@ -151,6 +151,8 @@ Variable name table scrambling creates protected BASIC programs that only use variable name scrambling. + **unprotbas -pv** also does variable name scrambling. + Bad next-line pointer Every line of tokenized BASIC contains a line length byte, which BASIC uses as a pointer to the next line of code. Before printing @@ -184,6 +186,8 @@ Bad next-line pointer fix bad pointers in protected programs, though it doesn't do anything about variable name scrambling. + **unprotbas -pc** also does this type of protection. + One more thing **unprotbas** can do is remove extra data from the end of the file. It's possible for BASIC files to contain extra data that occurs after the end of the program. Some programs use this as a way |