summaryrefslogtreecommitdiffstats
path: root/txr.1
diff options
context:
space:
mode:
Diffstat (limited to 'txr.1')
-rw-r--r--txr.144
1 files changed, 30 insertions, 14 deletions
diff --git a/txr.1 b/txr.1
index ea82953f..297759d9 100644
--- a/txr.1
+++ b/txr.1
@@ -68185,16 +68185,16 @@ is invoked on the aliasing array.
The meaning of the aliasing depends entirely on the bitwise representations of
the types involved.
-.coNP Functions @ carray-unum and @ carray-num
+.coNP Functions @ carray-uint and @ carray-int
.synb
-.mets (carray-unum < number <> [ type ])
-.mets (carray-num < number <> [ type ])
+.mets (carray-uint < number <> [ type ])
+.mets (carray-int < number <> [ type ])
.syne
.desc
The
-.code carray-unum
+.code carray-uint
and
-.code carray-num
+.code carray-int
functions convert
.metn number ,
an integer, to a binary image, which is then used as
@@ -68223,7 +68223,7 @@ than the storage provided by the array, it extended with padding bytes on the
left, near the beginning of the array.
In the case of
-.codn carray-unum ,
+.codn carray-uint ,
.meta number
must be a non-negative integer. An unsigned representation is produced
which carries no sign bit. The representation is as many bytes wide as
@@ -68232,7 +68232,7 @@ value is 1. If any padding bytes are required due to the array being larger,
they are always zero.
The
-.code carray-num
+.code carray-int
function encodes negative integers also, using a variable-length two's
complement representation. The number of bits required to hold the number
is calculated as the smallest width which can represent the value in two's
@@ -68245,28 +68245,28 @@ the padding bytes are filled with the value
.code #b11111111
(255) if the number is negative, or else 0 if it is non-negative.
-.coNP Functions @ unum-carray and @ num-carray
+.coNP Functions @ uint-carray and @ int-carray
.synb
-.mets (unum-carray << carray )
-.mets (num-carray < number <> [ type ])
+.mets (uint-carray << carray )
+.mets (int-carray < number <> [ type ])
.syne
.desc
The
-.code unum-carray
+.code uint-carray
and
-.code num-carray
+.code int-carray
functions treat the storage bytes
.meta carray
object as the representation of an integer.
The
-.code unum-carray
+.code uint-carray
function simply treats all of the bytes as a big-endian unsigned integer in
a pure binary representation, and returns that integer, which is necessarily
always non-negative.
The
-.code num-carray
+.code int-carray
function treats the bytes as a two's complement representation. The returned
number is negative if the first storage byte of
.meta carray
@@ -71134,6 +71134,22 @@ of these version values, the described behaviors are provided if
is given an argument which is equal or lower. For instance
.code "-C 103"
selects the behaviors described below for version 105, but not those for 102.
+.IP 227
+In \*(TX 227 and older versions, the functions
+.codn carray-uint ,
+.codn carray-int ,
+.code uint-carray
+and
+.code int-carray
+had different names, namely
+.codn carray-unum ,
+.codn carray-num ,
+.code unum-carray
+and
+.codn num-carray ,
+respectively.
+If 227 or lower compatibility is selected, these functions become
+available under their old names in addition to their new names.
.IP 225
After \*(TX 225, the behavior of the
.code do