From 3fa2da7ac8ad36e5b4febb6d1ed8713081e9d966 Mon Sep 17 00:00:00 2001 From: Juri Linkov Date: Mon, 17 Oct 2005 06:45:48 +0000 Subject: [PATCH] (Eval During Compile, Compiler Errors): Replace `...' with `@dots{}' in `@defmac' and `@defspec'. --- lispref/compile.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lispref/compile.texi b/lispref/compile.texi index 79ac366c27d..f8fd3f72b9a 100644 --- a/lispref/compile.texi +++ b/lispref/compile.texi @@ -401,7 +401,7 @@ it does nothing. It always returns @var{function}. These features permit you to write code to be evaluated during compilation of a program. -@defspec eval-and-compile body +@defspec eval-and-compile body@dots{} This form marks @var{body} to be evaluated both when you compile the containing code and when you run it (whether compiled or not). @@ -410,7 +410,7 @@ and referring to that file with @code{require}. That method is preferable when @var{body} is large. @end defspec -@defspec eval-when-compile body +@defspec eval-when-compile body@dots{} This form marks @var{body} to be evaluated at compile time but not when the compiled program is loaded. The result of evaluation by the compiler becomes a constant which appears in the compiled program. If @@ -470,7 +470,7 @@ The reference to @var{variable} must be in the @var{then-form} of the @c This is implemented with a defun, but conceptually it is @c a special form. -@defspec with-no-warnings body... +@defspec with-no-warnings body@dots{} In execution, this is equivalent to @code{(progn @var{body}...)}, but the compiler does not issue warnings for anything that occurs inside @var{body}. -- 2.11.4.GIT