diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2019-06-12 07:37:59 -0700 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2019-06-12 07:37:59 -0700 |
commit | 77ae026de432a7ecf1ddf779eb5529bf0e67ffce (patch) | |
tree | e1f41fc0ef2bfefca6890f813d39dcd39ac5490c /txr.1 | |
parent | 2032c68d012bd7ff0b31c49e09cca10c13e41ec0 (diff) | |
download | txr-77ae026de432a7ecf1ddf779eb5529bf0e67ffce.tar.gz txr-77ae026de432a7ecf1ddf779eb5529bf0e67ffce.tar.bz2 txr-77ae026de432a7ecf1ddf779eb5529bf0e67ffce.zip |
doc: no such thing as varray.
* txr.1: carray is contrasted with the FFI type varray; but
there is no such type. varray is a name used internally in the
implementation; it means "variable-length zarray".
Diffstat (limited to 'txr.1')
-rw-r--r-- | txr.1 | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -62161,15 +62161,15 @@ type is particularly useful in situations when foreign code generates such an array, and the size of that array isn't known from the object itself. -It is also useful, instead of -.code varray +It is also useful, instead of a variable-length +.code zarray for passing a dynamic array to foreign code in situations when the application benefits -from managing the memory for the array. The -.code varray +from managing the memory for the array. The variable-length +.code zarray FFI type's disadvantage relative to .code carray -is that -.code varray +is that the +.code zarray converts an entire Lisp sequence to a temporarily allocated array, which is used only for one call. By contrast, the .code carray |