summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2021-07-10 17:46:20 -0700
committerKaz Kylheku <kaz@kylheku.com>2021-07-10 17:46:20 -0700
commit0a94efb0cac257a4e1c62bbe51b68dc10e154433 (patch)
tree35b4dee32f757975501c15c517114d9241e22d4c
parent1e4995b77d391338bdf6eae58e4ca92c6c23f4d8 (diff)
downloadtxr-0a94efb0cac257a4e1c62bbe51b68dc10e154433.tar.gz
txr-0a94efb0cac257a4e1c62bbe51b68dc10e154433.tar.bz2
txr-0a94efb0cac257a4e1c62bbe51b68dc10e154433.zip
doc: finish incomplete sentence about hlet.
* txr.1: In a paragraph about the differences between compiled and interpretd behavior, complete a sentence about hlet/hlet* variables. Spotted by Paul A. Patience.
-rw-r--r--txr.18
1 files changed, 7 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index a1105a2c..917f5856 100644
--- a/txr.1
+++ b/txr.1
@@ -49007,7 +49007,13 @@ and
.code hlet*
can be used instead. These macros create variable bindings whose storage is
always outside of the stack, and therefore the variables will exhibit
-consistent
+consistent interpreted and compiled semantics under continuations.
+All contexts which capture the same lexical binding of a given
+.cod3 hlet / hlet*
+variable share a single instance. The most recent assignment
+to the variable taking place in any context establishes its value,
+as seen by any other context. The resumption of a continuation will not restore
+such a variable to a previous value.
If the affected variables are other kinds of bindings such as
function parameters or variables created with specialized binding