From: Richard M. Stallman <rms@gnu.org>
Date: Sat, 24 Nov 2007 16:00:21 +0000 (+0000)
Subject: (Compiler Errors): Clarify previous change.
X-Git-Tag: emacs-pretest-23.0.90~9494
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=fc37ae728d88a115c8e1b5c2d9d7705284e5f40e;p=emacs.git

(Compiler Errors): Clarify previous change.
---

diff --git a/doc/lispref/compile.texi b/doc/lispref/compile.texi
index fdd145ac9f1..292c52a6dfa 100644
--- a/doc/lispref/compile.texi
+++ b/doc/lispref/compile.texi
@@ -505,12 +505,14 @@ 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}).
+  You can tell the compiler that a function is defined using
+@code{declare-function} (@pxref{Declaring Functions}).  Likewise, you
+can tell the compiler that a variable is defined using @code{defvar}
+with no initial value.
 
-  Likewise, you can suppress a compiler warning for an unbound variable
-@var{variable} by conditionalizing its use on a @code{boundp} test,
-like this:
+  You can suppress the compiler warning for a specific use of an
+undefined variable @var{variable} by conditionalizing its use on a
+@code{boundp} test, like this:
 
 @example
 (if (boundp '@var{variable}) ...@var{variable}...)
@@ -521,11 +523,8 @@ 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}:
+  You can suppress any and all compiler warnings within a certain
+expression using the construct @code{with-no-warnings}:
 
 @c This is implemented with a defun, but conceptually it is
 @c a special form.
@@ -536,10 +535,11 @@ but the compiler does not issue warnings for anything that occurs
 inside @var{body}.
 
 We recommend that you use this construct around the smallest
-possible piece of code.
+possible piece of code, to avoid missing possible warnings other than one
+one you intend to suppress.
 @end defspec
 
-More precise control of warnings is possible by setting the variable
+  More precise control of warnings is possible by setting the variable
 @code{byte-compile-warnings}.
 
 @node Byte-Code Objects