summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2007-11-29 04:41:17 +0000
committerGlenn Morris <rgm@gnu.org>2007-11-29 04:41:17 +0000
commitc45400672ff7d5ab7df0a6dded2e35eb128b2f67 (patch)
treeb4967f4770b39b2e842f177245f8e0b3775d8438
parentcbfc51932ecee108ae7c7d1a694ad11bcbd1bfa4 (diff)
downloademacs-c45400672ff7d5ab7df0a6dded2e35eb128b2f67.tar.gz
(Declaring Functions): Add findex. Mention `external' files.
-rw-r--r--doc/lispref/functions.texi6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index 182d26511b1..b6f209c16d2 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -1227,6 +1227,7 @@ following the definition, just like macros.
@section Telling the Compiler that a Function is Defined
@cindex function declaration
@cindex declaring functions
+@findex declare-function
Byte-compiling a file often produces warnings about functions that the
compiler doesn't know about (@pxref{Compiler Errors}). Sometimes this
@@ -1289,6 +1290,11 @@ you call a function that is defined only on certain systems. Most
of the primitive functions of Emacs are always defined so they will
never give you a warning.
+ Sometimes a file will optionally use functions from an external package.
+If you prefix the filename in the @code{declare-function} statement with
+@samp{ext:}, then it will be checked if it is found, otherwise skipped
+without error.
+
@node Function Safety
@section Determining whether a Function is Safe to Call
@cindex function safety