procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify wording about functions' argument lists

Browse source 
* doc/lispref/functions.texi (Argument List): Clarify the
wording.  (Bug#31872)
This commit is contained in:
Eli Zaretskii 2018-06-23 10:38:44 +03:00
parent 5abac8bf81
commit decdfedf02
1 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/lispref/functions.texi
View file

@ -412,10 +412,14 @@ variables that tell you whether an argument was explicitly passed.
binds @code{a} and @code{b} to the first two actual arguments, which are binds @code{a} and @code{b} to the first two actual arguments, which are
required. If one or two more arguments are provided, @code{c} and required. If one or two more arguments are provided, @code{c} and
@code{d} are bound to them respectively; any arguments after the first @code{d} are bound to them respectively; any arguments after the first
four are collected into a list and @code{e} is bound to that list. If four are collected into a list and @code{e} is bound to that list.
there are only two arguments, @code{c} is @code{nil}; if two or three Thus, if there are only two arguments, @code{c}, @code{d} and @code{e}
arguments, @code{d} is @code{nil}; if four arguments or fewer, @code{e} are @code{nil}; if two or three arguments, @code{d} and @code{e} are
is @code{nil}. @code{nil}; if four arguments or fewer, @code{e} is @code{nil}. Note
that exactly five arguments with an explicit @code{nil} argument
provided for @code{e} will cause that @code{nil} argument to be passed
as a list with one element, @code{(nil)}, as with any other single
value for @code{e}.
There is no way to have required arguments following optional There is no way to have required arguments following optional
ones---it would not make sense. To see why this must be so, suppose ones---it would not make sense. To see why this must be so, suppose