From 6297397b28d2abdd11c1e715ec65368f5ef722fa Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Sat, 1 Dec 2007 02:32:20 +0000 Subject: [PATCH] (Declaring Functions): Improve previous change (arguments by name, not number). --- doc/lispref/functions.texi | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi index 1cd60f9009b..3767e778cf7 100644 --- a/doc/lispref/functions.texi +++ b/doc/lispref/functions.texi @@ -1298,11 +1298,12 @@ without error. There are some function definitions that @samp{check-declare} does not understand (e.g. @code{defstruct} and some other macros). In such cases, -you can pass a non-@code{nil} fourth argument to @code{declare-function}, -meaning to only check that the file exists, not that it actually defines -the function. Note that to do this without having to specify an -argument list, you should set the third argument to @code{t} (because -@code{nil} means an empty argument list, as opposed to an unspecified one). +you can pass a non-@code{nil} @var{fileonly} argument to +@code{declare-function}, meaning to only check that the file exists, not +that it actually defines the function. Note that to do this without +having to specify an argument list, you should set the @var{arglist} +argument to @code{t} (because @code{nil} means an empty argument list, as +opposed to an unspecified one). @node Function Safety @section Determining whether a Function is Safe to Call -- 2.39.2