diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2019-02-11 12:28:42 -0800 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2019-02-11 12:28:42 -0800 |
commit | 71e8f9979fcc7586137e5162e054539aadfdef2f (patch) | |
tree | fcf72133dc4124a5652f85f281b90dfbd3071abc | |
parent | 8e897f9d572bccf9d8324539853da133953ef12a (diff) | |
download | txr-71e8f9979fcc7586137e5162e054539aadfdef2f.tar.gz txr-71e8f9979fcc7586137e5162e054539aadfdef2f.tar.bz2 txr-71e8f9979fcc7586137e5162e054539aadfdef2f.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.1 | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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 |