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:
@@ -1,6 +1,6 @@
|
||||
10 REM A DEF call takes its environment from the pool, one per call, exactly as
|
||||
10 REM A DEF call takes one environment from the pool, exactly as
|
||||
20 REM GOSUB does. It used to be owned by the funcdef and reset on every call,
|
||||
30 REM which cost two silent defects: two calls in one expression shared a slot,
|
||||
30 REM which cost two silent defects: calls in one expression shared a slot,
|
||||
40 REM and recursion never came back at all.
|
||||
50 DEF FACT(N#)
|
||||
60 IF N# <= 1 THEN RETURN 1
|
||||
@@ -15,9 +15,9 @@
|
||||
150 DEF DBL(N#) = N# * 2
|
||||
160 PRINT DBL(10) + DBL(1)
|
||||
170 PRINT DBL(1) + DBL(10) + DBL(100)
|
||||
180 REM Depth answers to the environment pool now, so runaway recursion reports
|
||||
190 REM "Environment pool exhausted" rather than hanging. It is not exercised here
|
||||
200 REM because the statement containing a failed call still prints a junk value
|
||||
210 REM afterwards -- a separate, pre-existing defect recorded in TODO.md, and one
|
||||
220 REM this golden file would pin if it went in. tests/user_functions.c asserts
|
||||
180 REM Depth answers to the environment pool, so runaway recursion reports
|
||||
190 REM "Environment pool exhausted" rather than hanging. It is not exercised
|
||||
200 REM here because the failed statement still prints junk afterwards;
|
||||
210 REM this is a separate defect in TODO.md, and one this golden file
|
||||
220 REM would pin if it went in. tests/user_functions.c asserts
|
||||
230 REM the message instead.
|
||||
|
||||
Reference in New Issue
Block a user