Fix 80-column fixtures and tutorial expectations
All checks were successful
akbasic CI Build / cmake_build (push) Successful in 3m29s
akbasic CI Build / sanitizers (push) Successful in 4m42s
akbasic CI Build / coverage (push) Successful in 3m56s
akbasic CI Build / akgl_build (push) Successful in 8m34s
akbasic CI Build / mutation_test (push) Successful in 18m50s
All checks were successful
akbasic CI Build / cmake_build (push) Successful in 3m29s
akbasic CI Build / sanitizers (push) Successful in 4m42s
akbasic CI Build / coverage (push) Successful in 3m56s
akbasic CI Build / akgl_build (push) Successful in 8m34s
akbasic CI Build / mutation_test (push) Successful in 18m50s
This commit is contained in:
@@ -685,9 +685,9 @@ seconds asks for fifty frames a second.
|
||||
### Why `GOTO` rather than `DO ... LOOP`
|
||||
|
||||
A `DO ... LOOP` around the frame would read better, and it is not usable here: **a `GOTO`
|
||||
that jumps out of a `FOR` or a `DO` does not release the loop's scope.** There are 32
|
||||
that jumps out of a `FOR` or a `DO` does not release the loop's scope.** There are 12
|
||||
scopes, so a game that leaves its main loop once per lost life stops on the
|
||||
thirty-second one:
|
||||
twelfth one:
|
||||
|
||||
```basic
|
||||
N# = 0
|
||||
@@ -700,7 +700,7 @@ PRINT "SURVIVED " + N#
|
||||
```
|
||||
|
||||
```output
|
||||
? 3 : PARSE ERROR Environment pool exhausted at line 3 (32 in use)
|
||||
? 3 : PARSE ERROR Environment pool exhausted at line 3 (12 in use)
|
||||
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user