summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2019-02-11 12:28:42 -0800
committerKaz Kylheku <kaz@kylheku.com>2019-02-11 12:28:42 -0800
commit10e21ee8cc333b1e7d03b8ac22c4cc6bb7ca64e8 (patch)
treefcf72133dc4124a5652f85f281b90dfbd3071abc
parentf3e2007a7c5b75d5e4c726077418c4120349c36b (diff)
downloadtxr-10e21ee8cc333b1e7d03b8ac22c4cc6bb7ca64e8.tar.gz
txr-10e21ee8cc333b1e7d03b8ac22c4cc6bb7ca64e8.tar.bz2
txr-10e21ee8cc333b1e7d03b8ac22c4cc6bb7ca64e8.zip
doc: fix reference to nonexistent load-value.
* txr.1: In Notes under load-time, the function is once referred to as load-value; also the phrase load-time value is used that can just be load-time.
-rw-r--r--txr.14
1 files changed, 2 insertions, 2 deletions
diff --git a/txr.1 b/txr.1
index 454d752f..f4242042 100644
--- a/txr.1
+++ b/txr.1
@@ -63955,7 +63955,7 @@ closure which is returned. Invoking the closure doesn't cause the
expressions to be evaluated.
The use of
-.code load-value
+.code load-time
is similar to defining a variable and then referring to the variable.
For instance, a file containing this:
@@ -63995,7 +63995,7 @@ The advantage of
is that it doesn't require a separate top-level form to achieve its load-time
effect: the expression is simply nested at the point where it is needed. The
.code load-time
-value form can therefore be generated by macros, whose expansions cannot inject
+form can therefore be generated by macros, whose expansions cannot inject
extra top-level forms into the site where they are invoked.
If a macro writer would like some form to be evaluated at load time and
its value accessible in a macro expansion that appears arbitrarily nested