changeset 54021:5cd1edd36679

(Compiler Errors): if-boundp feature applies to cond.
author Richard M. Stallman <rms@gnu.org>
date Mon, 16 Feb 2004 22:10:42 +0000
parents 2d72c05c1ea8
children 118899be0578
files lispref/compile.texi
diffstat 1 files changed, 5 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/compile.texi	Mon Feb 16 22:09:52 2004 +0000
+++ b/lispref/compile.texi	Mon Feb 16 22:10:42 2004 +0000
@@ -448,9 +448,11 @@
 @end example
 
 @noindent
-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}.
-Likewise, you can suppress a compiler warning for an unbound variable
+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.)
+
+  Likewise, you can suppress a compiler warning for an unbound variable
 @var{variable} by conditionalizing its use on a @code{boundp} test,
 like this: