[Emacs-diffs] Changes to emacs/doc/lispref/functions.texi,v

[Glenn Morris]

CVSROOT:        /sources/emacs
Module name:    emacs
Changes by:     Glenn Morris <gm>       07/11/30 07:51:29

Index: functions.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/lispref/functions.texi,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- functions.texi      29 Nov 2007 04:41:17 -0000      1.7
+++ functions.texi      30 Nov 2007 07:51:29 -0000      1.8
@@ -1266,10 +1266,11 @@
 You don't have to specify the argument list, but if you do the
 byte compiler can check that the calls match the declaration.
 
address@hidden declare-function function file arglist
address@hidden declare-function function file &optional arglist fileonly
 Tell the byte compiler to assume that @var{function} is defined, with
 arguments @var{arglist}, and that the definition should come from
-the file @var{file}.
+the file @var{file}.  @var{fileonly} non-nil means only check that
address@hidden exists, not that it actually defines @var{function}.
 @end defmac
 
   To verify that these functions really are declared where
@@ -1295,6 +1296,14 @@
 @samp{ext:}, then it will be checked if it is found, otherwise skipped
 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 address@hidden 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
address@hidden means an empty argument list, as opposed to an unspecified one).
+
 @node Function Safety
 @section Determining whether a Function is Safe to Call
 @cindex function safety