Mercurial > emacs
changeset 86384:cb294fc4a594
(Compiler Errors): Mention declaring functions, defvar with no
initvalue, and byte-compile-warnings.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Sat, 24 Nov 2007 03:06:33 +0000 |
parents | 382d8b0539b2 |
children | 7273972e1566 |
files | doc/lispref/compile.texi |
diffstat | 1 files changed, 9 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/lispref/compile.texi Sat Nov 24 03:06:15 2007 +0000 +++ b/doc/lispref/compile.texi Sat Nov 24 03:06:33 2007 +0000 @@ -505,6 +505,9 @@ @code{if}, and @var{func} must appear quoted in the call to @code{fboundp}. (This feature operates for @code{cond} as well.) + You can tell the compiler that a function is defined using a +@code{declare-function} statement (@pxref{Declaring Functions}). + Likewise, you can suppress a compiler warning for an unbound variable @var{variable} by conditionalizing its use on a @code{boundp} test, like this: @@ -518,6 +521,9 @@ @code{if}, and @var{variable} must appear quoted in the call to @code{boundp}. + You can tell the compiler that a variable is defined using a +@code{defvar} statement with no initial value. + You can suppress any compiler warnings using the construct @code{with-no-warnings}: @@ -533,6 +539,9 @@ possible piece of code. @end defspec +More precise control of warnings is possible by setting the variable +@code{byte-compile-warnings}. + @node Byte-Code Objects @section Byte-Code Function Objects @cindex compiled function