diff options
| author | Richard M. Stallman | 2003-07-14 16:00:44 +0000 |
|---|---|---|
| committer | Richard M. Stallman | 2003-07-14 16:00:44 +0000 |
| commit | d7810bdaaeda822de1f74309f7981c542cf9035e (patch) | |
| tree | 4900720453336618d17839293972acc2cd42e57c | |
| parent | dd726314b834da686132f5723793899d8646bdbc (diff) | |
| download | emacs-d7810bdaaeda822de1f74309f7981c542cf9035e.tar.gz emacs-d7810bdaaeda822de1f74309f7981c542cf9035e.zip | |
(Byte Compilation): Explain no-byte-compile
(Compiler Errors): New node.
| -rw-r--r-- | lispref/compile.texi | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/lispref/compile.texi b/lispref/compile.texi index c5615b0ec5e..583454efe73 100644 --- a/lispref/compile.texi +++ b/lispref/compile.texi | |||
| @@ -39,6 +39,14 @@ Emacs 19.29; as a result, files compiled in versions before 19.29 will | |||
| 39 | not work in subsequent versions if they contain character constants with | 39 | not work in subsequent versions if they contain character constants with |
| 40 | modifier bits. | 40 | modifier bits. |
| 41 | 41 | ||
| 42 | @vindex no-byte-compile | ||
| 43 | If you do not want a Lisp file to be compiled, ever, put a file-local | ||
| 44 | variable binding for @code{no-byte-compile} into it, like this: | ||
| 45 | |||
| 46 | @example | ||
| 47 | ;; -*-no-byte-compile: t; -*- | ||
| 48 | @end example | ||
| 49 | |||
| 42 | @xref{Compilation Errors}, for how to investigate errors occurring in | 50 | @xref{Compilation Errors}, for how to investigate errors occurring in |
| 43 | byte compilation. | 51 | byte compilation. |
| 44 | 52 | ||
| @@ -48,6 +56,7 @@ byte compilation. | |||
| 48 | * Docs and Compilation:: Dynamic loading of documentation strings. | 56 | * Docs and Compilation:: Dynamic loading of documentation strings. |
| 49 | * Dynamic Loading:: Dynamic loading of individual functions. | 57 | * Dynamic Loading:: Dynamic loading of individual functions. |
| 50 | * Eval During Compile:: Code to be evaluated when you compile. | 58 | * Eval During Compile:: Code to be evaluated when you compile. |
| 59 | * Compiler Errors:: Handling compiler error messages. | ||
| 51 | * Byte-Code Objects:: The data type used for byte-compiled functions. | 60 | * Byte-Code Objects:: The data type used for byte-compiled functions. |
| 52 | * Disassembly:: Disassembling byte-code; how to read byte-code. | 61 | * Disassembly:: Disassembling byte-code; how to read byte-code. |
| 53 | @end menu | 62 | @end menu |
| @@ -397,6 +406,21 @@ Common Lisp @samp{#.} reader macro (but not when interpreting) is closer | |||
| 397 | to what @code{eval-when-compile} does. | 406 | to what @code{eval-when-compile} does. |
| 398 | @end defspec | 407 | @end defspec |
| 399 | 408 | ||
| 409 | @node Compiler Errors | ||
| 410 | @section Compiler Errors | ||
| 411 | @cindex compiler errors | ||
| 412 | |||
| 413 | Byte compilation writes errors and warnings into the buffer | ||
| 414 | @samp{*Compile-Log*}. The messages include file names and line | ||
| 415 | numbers that identify the location of the problem. The usual Emacs | ||
| 416 | commands for operating on compiler diagnostics work properly on | ||
| 417 | these messages. | ||
| 418 | |||
| 419 | However, the warnings about functions that were used but not | ||
| 420 | defined are always ``located'' at the end of the file, so these | ||
| 421 | commands won't find the places they are really used. To do that, | ||
| 422 | you must search for the function names. | ||
| 423 | |||
| 400 | @node Byte-Code Objects | 424 | @node Byte-Code Objects |
| 401 | @section Byte-Code Function Objects | 425 | @section Byte-Code Function Objects |
| 402 | @cindex compiled function | 426 | @cindex compiled function |