(Bindat Spec): Clarify using field names in

length specifications.

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 5e66dd7bf9d6bb96b67e33ba63d5d9f0b9b1675d..955d25e64c391a3b80a9d05f3d57757df0e31e19 100644 (file)
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2006-12-30  Kim F. Storm  <storm@cua.dk>
+
+       * processes.texi (Bindat Spec): Clarify using field names in
+       length specifications.
+
 2006-12-29  Kim F. Storm  <storm@cua.dk>
 
        * processes.texi (Bindat Spec): Explain eval forms and lengths better.

diff --git a/lispref/processes.texi b/lispref/processes.texi
index 3992d79fca0e79c96da6c78772c762b64426cbc1..2fd1f5ec96349b6913d8fa76b745c59163d6db42 100644 (file)
--- a/lispref/processes.texi
+++ b/lispref/processes.texi
@@ -2166,13 +2166,15 @@ unpacked or packed.  The result of the evaluation should be one of the
 above-listed type specifications.
 @end table
 
-For a fixed-size field, the length @var{len} is given as an
-integer specifying the number of bytes in the field.  When the
-length of a field is not fixed, it typically depends on the value of a
-preceding field.  In this case, the length can be given either by
-that field's name as specified for @code{bindat-get-field} below, or by
-an expression @code{(eval @var{form})} where @var{form} should
-evaluate to an integer, specifying the field length.
+For a fixed-size field, the length @var{len} is given as an integer
+specifying the number of bytes in the field.
+
+When the length of a field is not fixed, it typically depends on the
+value of a preceding field.  In this case, the length @var{len} can be
+given either as a list @code{(@var{name} ...)} identifying a
+@dfn{field name} in the format specified for @code{bindat-get-field}
+below, or by an expression @code{(eval @var{form})} where @var{form}
+should evaluate to an integer, specifying the field length.
 
 A field specification generally has the form @code{([@var{name}]
 @var{handler})}.  The square braces indicate that @var{name} is