summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2021-06-17 06:48:09 -0700
committerKaz Kylheku <kaz@kylheku.com>2021-06-17 06:48:09 -0700
commitf564f9a7d4c5c660f6603682d5019249ed8c809b (patch)
treef0de527237362cf125917a135717f4806ad18161
parent4bafb40f4277684435756bf9191b9810655e25a1 (diff)
downloadtxr-f564f9a7d4c5c660f6603682d5019249ed8c809b.tar.gz
txr-f564f9a7d4c5c660f6603682d5019249ed8c809b.tar.bz2
txr-f564f9a7d4c5c660f6603682d5019249ed8c809b.zip
doc: bad grammar under FFI ptr type
* txr.1: "update *the* datum".
-rw-r--r--txr.12
1 files changed, 1 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index bdd6fa71..20e0a241 100644
--- a/txr.1
+++ b/txr.1
@@ -74536,7 +74536,7 @@ using a C pointer as the external representation.
When used for passing a value to a foreign function, the
.code ptr
type has in-out semantics: it supports the interfacing concept that
-the called function can update datum which has been passed to it "by pointer",
+the called function can update the datum which has been passed to it "by pointer",
thereby altering the caller's object. Since a Lisp value requires a conversion
to the FFI external representation, it cannot be directly passed by pointer.
Instead, this semantics is simulated. The put semantics of