comparison lispref/compile.texi @ 38160:05a836654c88

(Compilation Functions): Add xref to Problems with Macros.
author Richard M. Stallman <rms@gnu.org>
date Sat, 23 Jun 2001 16:08:32 +0000
parents d4ac295a98b3
children 23a1cea22d13
comparison
equal deleted inserted replaced
38159:4c01e54e2ffd 38160:05a836654c88
108 108
109 @cindex macro compilation 109 @cindex macro compilation
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
111 byte-compile. Macro calls are expanded when they are compiled, so the 111 byte-compile. Macro calls are expanded when they are compiled, so the
112 macros must already be defined for proper compilation. For more 112 macros must already be defined for proper compilation. For more
113 details, see @ref{Compiling Macros}. 113 details, see @ref{Compiling Macros}. If a program does not work the
114 same way when compiled as it does when interpreted, erroneous macro
115 definitions 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
116 load the file. But it does execute any @code{require} calls at top 118 load the file. But it does execute any @code{require} calls at top
117 level in the file. One way to ensure that necessary macro definitions 119 level in the file. One way to ensure that necessary macro definitions
118 are available during compilation is to require the file that defines 120 are available during compilation is to require the file that defines