From 5c5114b7ec02b72c66c4cc5d3228124ce92dd2a0 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 16 Feb 2004 22:10:42 +0000 Subject: [PATCH] (Compiler Errors): if-boundp feature applies to cond. --- lispref/compile.texi | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/lispref/compile.texi b/lispref/compile.texi index 960b00dd6fc..a201a225379 100644 --- a/lispref/compile.texi +++ b/lispref/compile.texi @@ -448,9 +448,11 @@ function @var{func} by conditionalizing the function call on a @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: -- 2.39.2