Loops, and the scripting language is a language

while and for. Both only mean anything in a script, because a loop goes back to
the line that opened it and a prompt has no line to go back to - and both say so
rather than doing something surprising.

THE SCRIPT READER KEEPS THE POSITION OF EVERY LINE before reading it, which is
what makes any of this possible: by the time a line has been read the reader is
past it, and a line is not a fixed size to subtract. Three words per line, and
the block is read again on the way back so the pointer into it means what it
meant - the same thing nesting one script inside another already did, for a
different reason.

THE TWO LOOPS END DIFFERENTLY, and that is the design rather than an accident. A
while is taken away at its end and its own line asks the question again, so
nothing has to be remembered. A for is not: how many words it has used is kept
in the block, and its line reads itself again and counts one more off the front.
That is a byte in a block instead of a copy of the word list in every one of
them.

Blocks grew from a byte to a record of sixteen - state, kind, words used, and
where the line that opened it was - and sixteen because A and B are a shift
register, so four rotations turn a block number into its offset. The history and
the variables are addressed the same way for the same reason.

Nested loops, an if inside a loop, a loop inside a branch nobody takes, and a for
with no words: the last two run no times rather than once, which is the case
worth having a test for.

Three things found by running it:

textSame asks whether two WHOLE strings are the same, so "in red green blue" is
not "in". The word has to be split off before it is compared.

A for typed at a prompt complained about while, because both arrive at the same
place. One message that names neither is better than one that names the wrong
one.

And docs.sh caught a naming convention nobody had written down: it recognises a
packed name by its label ending in "Name", so ForName2 was silently not counted.
It failed the right way round - saying the run was shorter than the count claims
rather than passing - but the convention now lives where the names are and not
only in the checker.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Tests/manifest

@@ -438,6 +438,18 @@ cosmosStack          | CosmOS/Source/cosmos.asm           | run      | cosmosSta
 # set, inside the branch that is not taken, and that must not be an error - so the skipping
 # happens before the names are filled in, and a line nobody is running cannot fail.
 cosmosBlocks         | CosmOS/Source/cosmos.asm           | run      | cosmosBlocks.in    | -     | disks/cosmos.img
+# And the two loops. Both go back to the line that opened them, which is why the script
+# reader keeps the position of every line before reading it: by the time a line has been read
+# the reader is past it, and a line is not a fixed size to subtract.
+#
+# A while is TAKEN AWAY at its end and its line asks the question again. A for is not: what it
+# has used is in the block, and the line reads itself again and counts one more word off the
+# front - which is a byte in a block rather than a copy of the list in each one.
+#
+# Nested loops, an if inside a loop, a loop inside a branch nobody takes, and a for with no
+# words at all, which runs no times rather than once. Neither loop makes sense typed at a
+# prompt, and both say so.
+cosmosLoops          | CosmOS/Source/cosmos.asm           | run      | cosmosLoops.in     | -     | disks/cosmos.img
 # The same editing offered to a PROGRAM, through osReadLine. Edit reads its lines that way,
 # so a word typed with two letters the wrong way round is put right without starting the line
 # again - which is the whole of what A4 buys.