+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.
@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:
@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}:
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