39 |
not work in subsequent versions if they contain character constants with |
not work in subsequent versions if they contain character constants with |
40 |
modifier bits. |
modifier bits. |
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 |
|
|
50 |
@xref{Compilation Errors}, for how to investigate errors occurring in |
@xref{Compilation Errors}, for how to investigate errors occurring in |
51 |
byte compilation. |
byte compilation. |
52 |
|
|
56 |
* Docs and Compilation:: Dynamic loading of documentation strings. |
* Docs and Compilation:: Dynamic loading of documentation strings. |
57 |
* Dynamic Loading:: Dynamic loading of individual functions. |
* Dynamic Loading:: Dynamic loading of individual functions. |
58 |
* Eval During Compile:: Code to be evaluated when you compile. |
* Eval During Compile:: Code to be evaluated when you compile. |
59 |
|
* Compiler Errors:: Handling compiler error messages. |
60 |
* Byte-Code Objects:: The data type used for byte-compiled functions. |
* Byte-Code Objects:: The data type used for byte-compiled functions. |
61 |
* Disassembly:: Disassembling byte-code; how to read byte-code. |
* Disassembly:: Disassembling byte-code; how to read byte-code. |
62 |
@end menu |
@end menu |
406 |
to what @code{eval-when-compile} does. |
to what @code{eval-when-compile} does. |
407 |
@end defspec |
@end defspec |
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 |
|
|
424 |
@node Byte-Code Objects |
@node Byte-Code Objects |
425 |
@section Byte-Code Function Objects |
@section Byte-Code Function Objects |
426 |
@cindex compiled function |
@cindex compiled function |