aboutsummaryrefslogtreecommitdiff
path: root/ONBOARD.md
diff options
context:
space:
mode:
authorGravatar zinc <zinc@downsta.ir> 2026-10-14 15:52:01 +0330
committerGravatar zinc <zinc@downsta.ir> 2026-10-14 15:52:01 +0330
commit4fc8f54a21f7a9d8712665501b40c3a52b3eede9 (patch)
treefcb16d3185c1f80fae8d54cd9062bd68d6c0c88d /ONBOARD.md
parentline tables and backtraces: port agent/line-tables onto main, op 56 on the x8... (diff)
parentmerge spec conformance suite (diff)
merge main into work/line-tables
Diffstat (limited to 'ONBOARD.md')
-rw-r--r--ONBOARD.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/ONBOARD.md b/ONBOARD.md
index 47e1cba..35d5e35 100644
--- a/ONBOARD.md
+++ b/ONBOARD.md
@@ -130,6 +130,8 @@ read in this order:
to see the compiler as one text, as the bootstrap does, run
`cat $(sed 's|^|src/compiler/|' src/compiler/parts)`.
+the state is mostly global arrays and scalars that distant functions read and write: run `make xref` before changing compiler state, and read `build/xref/report.txt` for who writes the global and who only reads it (`make xref XREF_ARGS=--check` compares with `tests/xref.baseline`).
+
you should be able to say where a new keyword is registered, how a keyword
works at the top level and inside a function, and how the compiler emits a
byte-string literal into the code stream.