# HG changeset patch
# User Juri Linkov <juri@jurta.org>
# Date 1129531548 0
# Node ID 2af75f8155de339d5e431adecff542a0c20acf45
# Parent  8dc3a4b8291f16ee7aa8e4bcc390be817a4b82c1
(Eval During Compile, Compiler Errors):
Replace `...' with `@dots{}' in `@defmac' and `@defspec'.

diff -r 8dc3a4b8291f -r 2af75f8155de lispref/compile.texi
--- a/lispref/compile.texi	Mon Oct 17 06:45:26 2005 +0000
+++ b/lispref/compile.texi	Mon Oct 17 06:45:48 2005 +0000
@@ -401,7 +401,7 @@
   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 @@
 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 @@
 @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}.