# HG changeset patch
# User Kim F. Storm <storm@cua.dk>
# Date 1167440093 0
# Node ID d278931df0ddd3632d7e4886d57c3b2cc7ef0475
# Parent  3b49658358de82ca8cdf2d721b1c0b94f3e02a22
(Bindat Spec): Clarify using field names in
length specifications.

diff -r 3b49658358de -r d278931df0dd lispref/processes.texi
--- a/lispref/processes.texi	Fri Dec 29 23:57:38 2006 +0000
+++ b/lispref/processes.texi	Sat Dec 30 00:54:53 2006 +0000
@@ -2166,13 +2166,15 @@
 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