Mercurial > emacs
changeset 39168:0317f0f05c37
Minor clarification.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Thu, 06 Sep 2001 19:50:20 +0000 |
| parents | 97f7986f0b80 |
| children | 338b1a97adf7 |
| files | lispref/functions.texi lispref/text.texi |
| diffstat | 2 files changed, 9 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/functions.texi Thu Sep 06 19:49:21 2001 +0000 +++ b/lispref/functions.texi Thu Sep 06 19:50:20 2001 +0000 @@ -364,9 +364,11 @@ There is no way to have required arguments following optional ones---it would not make sense. To see why this must be so, suppose that @code{c} in the example were optional and @code{d} were required. -Suppose three actual arguments are given; which variable would the third -argument be for? Similarly, it makes no sense to have any more -arguments (either required or optional) after a @code{&rest} argument. +Suppose three actual arguments are given; which variable would the +third argument be for? Would it be used for the @var{c}, or for +@var{d}? One can argue for both possibilities. Similarly, it makes +no sense to have any more arguments (either required or optional) +after a @code{&rest} argument. Here are some examples of argument lists and proper calls:
--- a/lispref/text.texi Thu Sep 06 19:49:21 2001 +0000 +++ b/lispref/text.texi Thu Sep 06 19:50:20 2001 +0000 @@ -3513,10 +3513,10 @@ @section Base 64 Encoding @cindex base 64 encoding - Base 64 code is used in email to encode a sequence of 8-bit bytes as a -longer sequence of @sc{ascii} graphic characters. It is defined in RFC -2045. This section describes the functions for converting to and from -this code. + Base 64 code is used in email to encode a sequence of 8-bit bytes as +a longer sequence of @sc{ascii} graphic characters. It is defined in +Internet RFC 2045. This section describes the functions for +converting to and from this code. @defun base64-encode-region beg end &optional no-line-break @tindex base64-encode-region