some comment stuff, and implement "keyword"

Force-Push: yes
Change-Id: Iecf4079b9629f9c041b7fe994b1a69b6ef7b6dd0

1 files changed, 5 insertions, 11 deletions

diff --git a/log-load.e b/log-load.e
index 4649403..9f8a8b7 100644
--- a/log-load.e
+++ b/log-load.e
@@ -314,18 +314,12 @@
 
 
 ~   A keyword is a word that evaluates to its own address, which makes it
-~ suitable for use as a constant. By convention, all our keywords have names
-~ starting with a colon, which imitates the way they work in Common Lisp.
+~ suitable for use as a constant. See more detail on that in interpret.e,
+~ where "keyword" is defined.
 ~
-~   Specifically, it returns its own execution token. Thus, executing its
-~ result repeatedly will keep giving the same value. We aren't in the habit of
-~ doing quote-exec kinds of things in Evocation, but it seems as good as any
-~ other unique value, so we might as well.
-~
-~   Unlike CL, we don't currently have the lexer automatically create keywords
-~ for us; we create them explicitly. Even if we did someday have it be
-~ automatic, the log-load routine would need a way to do it explicitly, which
-~ is this.
+~   Unlike Common Lisp, the lexer doesn't create keywords for us, we have to
+~ do it explicitly. If if that were to someday change, the log-load routine
+~ would still need a way to do it, which is this.
 ~
 ~   It's kind of a pain to look up the appropriate "docol" from here, so we
 ~ do it in assembler instead.