summaryrefslogtreecommitdiff
path: root/doc/0
diff options
context:
space:
mode:
Diffstat (limited to 'doc/0')
-rw-r--r--doc/0/0-value.md16
-rw-r--r--doc/0/1-parse.md12
-rw-r--r--doc/0/index.md4
3 files changed, 16 insertions, 16 deletions
diff --git a/doc/0/0-value.md b/doc/0/0-value.md
index 4bb7e0c..16e1a58 100644
--- a/doc/0/0-value.md
+++ b/doc/0/0-value.md
@@ -166,21 +166,21 @@ with small payload values here: There is room for over 268 Million 16-bit types
The final 51-bit range is used for various internal purposes by the Zisp
interpreter, mostly related to transparent code optimization.
- 000 :: Pointer to heap object as constant
+ 000 :: Pointer to heap object as constant
- 001 :: Pointer to list values as constant
+ 001 :: Pointer to list values as constant
- 010 :: Pointer to istr object as constant
+ 010 :: Pointer to istr object as constant
- 011 :: Immediate short string as constant
+ 011 :: Immediate short string as constant
- 100 :: Local variable reference by index
+ 100 :: Local variable reference by index
- 101 :: Pointer to constant function-call expression
+ 101 :: Pointer to constant function-call expression
- 110 :: Pointer to variable function-call expression
+ 110 :: Pointer to variable function-call expression
- 111 :: Pointer to special-form or macro-call expression
+ 111 :: Pointer to special-form or macro-call expression
Forbidden Value #4, Positive Infinity, is avoided thanks to the fact that heap
pointers always have a non-zero heap-type tag. (See further above.)
diff --git a/doc/0/1-parse.md b/doc/0/1-parse.md
index 101a3b6..32ffa2f 100644
--- a/doc/0/1-parse.md
+++ b/doc/0/1-parse.md
@@ -260,14 +260,14 @@ the parser to generate a list with the structure:
(#PQSTR <STRING>) ;; <STRING> is visual aid, not syntax
The decoder, using default settings, would emit this string verbatim as a value.
-Then, during code evaluation, this would be seen as an identifier. In this way,
+Then, during code execution, this would be seen as an identifier. In this way,
pipe-quoted strings are equivalent to bare strings in functionality.
It is important to understand that the decoder sits between the parser and the
-[evaluator](3-eval.html), and in opposition to Lisp and Scheme tradition, it is
-common for the evaluator to receive values that are not valid as a datum; here,
-a string unto itself that may not be a valid datum. Yet, it is valid as an
-identifier for the purposes of the evaluator.
+[interpreter](3-execute.html), and in opposition to Lisp and Scheme tradition,
+it is common for the interpreter to receive values that are not valid as data;
+here, a string unto itself that may not be a valid datum. Yet, it is valid as
+an identifier value for the purposes of the interpreter.
### Double-quoted
@@ -524,7 +524,7 @@ Notes:
* Syntax sugar can combine arbitrarily. Some examples follow. Any of these may
or may not actually have a meaning in code; some might simply end up producing
- an error during decoding, or later evaluation of code.
+ an error during decoding, or later execution, of code.
#{...} -> (#HASH (#BRACE ...))
diff --git a/doc/0/index.md b/doc/0/index.md
index f0da216..844729c 100644
--- a/doc/0/index.md
+++ b/doc/0/index.md
@@ -20,9 +20,9 @@ compiling code.
over data received from the parser, enriching it with more complex
value types, and handling primitive source code transforms.
-3. [Eval](3-eval.html)
+3. [Execute](3-execute.html)
- Code is evaluated within a mutable module context, on which it can
+ Code is executed within a mutable module context, on which it can
have side effects such as creating new definitions or establishing
links to other modules.