Commit 5bb0cda3 authored by Glenn Morris's avatar Glenn Morris

(Compiler Errors): Mention declaring functions, defvar with no

initvalue, and byte-compile-warnings.
parent e31dfb12
2007-11-24 Glenn Morris <rgm@gnu.org>
* functions.texi (Declaring Functions): New section.
* compile.texi (Compiler Errors): Mention declaring functions,
defvar with no initvalue, and byte-compile-warnings.
2007-11-15 Martin Rudalics <rudalics@gmx.at>
* vol1.texi (Top): Remove Frame-Local Variables from Node Listing.
......
......@@ -505,6 +505,9 @@ The call to @var{func} must be in the @var{then-form} of the
@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 @@ The reference to @var{variable} must be in the @var{then-form} of the
@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 @@ We recommend that you use this construct around the smallest
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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment