From 067e9a04dbce2b36d8094ab3aa7dc0c934d9486c Mon Sep 17 00:00:00 2001 From: Taylan Kammer Date: Sat, 3 Jan 2026 01:41:45 +0100 Subject: Fix links in notes. --- notes/250219-reader.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'notes/250219-reader.md') diff --git a/notes/250219-reader.md b/notes/250219-reader.md index 6e604f4..de71b4e 100644 --- a/notes/250219-reader.md +++ b/notes/250219-reader.md @@ -5,15 +5,15 @@ _2025 February_ *This started from an expansion to the following, then became its own article:* -[Symbols are strings are symbols](symbols.html) +[Symbols are strings are symbols](250210-symbols.html) OK but hear me out... What if there were different reader modes, for code and (pure) data? -I want Zisp to have various neat [syntactic extensions](sugar.html) -for programming purposes anyway, like the lambda shorthand, and these -shouldn't apply to configuration files, either. (Although they seem -unlikely to occur by accident.) +I want Zisp to have various neat syntactic extensions (see [syntax +sugar](250210-sugar.html) note) for programming purposes anyway, like +the lambda shorthand, and these shouldn't apply to configuration +files, either. (Although they seem unlikely to occur by accident.) So what if the transform from string literal to quoted string literal only occurred in code reading mode? @@ -154,7 +154,7 @@ Typical pipeline when reading and evaluating code: rune calls to produce values i.e. desugars code & compiles code -Reading in a [serialized program](compile.html): +Reading in a [serialized program](250210-compile.html): data-file --[data-reader]--> data --[eval]--> values ^^^^ @@ -284,8 +284,8 @@ The following exist: 1. Decoder: Calls decoders for runes in data, to yield values. - 2. Evaluator: [Executes aka compiles](compile.html) decoded values - into other values.[*] + 2. Evaluator: [Executes aka compiles](250210-compile.html) decoded + values into other values.[*] 3. Reverse in-memory transformers: @@ -406,7 +406,7 @@ to allow arbitrary code execution to happen just when reading a data file and decoding it. So something exceptional would need to happen for this to work. Or maybe not. -Remember that [compilation is execution](compile.html) in Zisp, +Remember that [compilation is execution](250210-compile.html) in Zisp, meaning that compiling a file looks like this in pseudo-Scheme: (define env (null-environment)) ;start out empty -- cgit v1.2.3