aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--lispref/compile.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/lispref/compile.texi b/lispref/compile.texi
index 001466d500d..b854fc86edf 100644
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -110,7 +110,9 @@ program that suggest a problem but are not necessarily erroneous.
110 Be careful when writing macro calls in files that you may someday 110 Be careful when writing macro calls in files that you may someday
111byte-compile. Macro calls are expanded when they are compiled, so the 111byte-compile. Macro calls are expanded when they are compiled, so the
112macros must already be defined for proper compilation. For more 112macros must already be defined for proper compilation. For more
113details, see @ref{Compiling Macros}. 113details, see @ref{Compiling Macros}. If a program does not work the
114same way when compiled as it does when interpreted, erroneous macro
115definitions are one likely cause (@pxref{Problems with Macros}).
114 116
115 Normally, compiling a file does not evaluate the file's contents or 117 Normally, compiling a file does not evaluate the file's contents or
116load the file. But it does execute any @code{require} calls at top 118load the file. But it does execute any @code{require} calls at top