diff options
Diffstat (limited to 'doc/0/1-parse.md')
| -rw-r--r-- | doc/0/1-parse.md | 12 |
1 files changed, 6 insertions, 6 deletions
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 ...)) |