comparison lispref/functions.texi @ 39168:0317f0f05c37

Minor clarification.
author Richard M. Stallman <rms@gnu.org>
date Thu, 06 Sep 2001 19:50:20 +0000
parents 82306439b33d
children 3e0b4b8d4f7e
comparison
equal deleted inserted replaced
39167:97f7986f0b80 39168:0317f0f05c37
362 is @code{nil}. 362 is @code{nil}.
363 363
364 There is no way to have required arguments following optional 364 There is no way to have required arguments following optional
365 ones---it would not make sense. To see why this must be so, suppose 365 ones---it would not make sense. To see why this must be so, suppose
366 that @code{c} in the example were optional and @code{d} were required. 366 that @code{c} in the example were optional and @code{d} were required.
367 Suppose three actual arguments are given; which variable would the third 367 Suppose three actual arguments are given; which variable would the
368 argument be for? Similarly, it makes no sense to have any more 368 third argument be for? Would it be used for the @var{c}, or for
369 arguments (either required or optional) after a @code{&rest} argument. 369 @var{d}? One can argue for both possibilities. Similarly, it makes
370 no sense to have any more arguments (either required or optional)
371 after a @code{&rest} argument.
370 372
371 Here are some examples of argument lists and proper calls: 373 Here are some examples of argument lists and proper calls:
372 374
373 @smallexample 375 @smallexample
374 ((lambda (n) (1+ n)) ; @r{One required:} 376 ((lambda (n) (1+ n)) ; @r{One required:}