mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-06-10 14:00:21 +02:00
Document `%auto-compilation-options'.
* doc/ref/api-evaluation.texi (Compilation): Emphasize auto-compilation. Document `%auto-compilation-options'.
This commit is contained in:
parent
bb5b36d069
commit
14d2ee3116
1 changed files with 11 additions and 3 deletions
|
@ -534,11 +534,13 @@ interpreter.
|
|||
Functions from system modules in a Guile installation are normally
|
||||
compiled already, so they load and run quickly.
|
||||
|
||||
@cindex automatic compilation
|
||||
Note that well-written Scheme programs will not typically call the
|
||||
procedures in this section, for the same reason that it is often bad
|
||||
taste to use @code{eval}. The normal interface to the compiler is the
|
||||
command-line file compiler, which can be invoked from the shell as
|
||||
@code{guile-tools compile foo.scm}.
|
||||
taste to use @code{eval}. By default, Guile automatically compiles any
|
||||
files it encounters that have not been compiled yet (@pxref{Invoking
|
||||
Guile, @code{--auto-compile}}). The compiler can also be invoked
|
||||
explicitly from the shell as @code{guile-tools compile foo.scm}.
|
||||
|
||||
(Why are calls to @code{eval} and @code{compile} usually in bad taste?
|
||||
Because they are limited, in that they can only really make sense for
|
||||
|
@ -638,6 +640,12 @@ should pass the @var{output-file} option to @code{compile-file},
|
|||
explicitly.
|
||||
@end deffn
|
||||
|
||||
@defvr {Scheme Variable} %auto-compilation-options
|
||||
This variable contains the options passed to the @code{compile-file}
|
||||
procedure when auto-compiling source files. By default, it enables
|
||||
useful compilation warnings. It can be customized from @file{~/.guile}.
|
||||
@end defvr
|
||||
|
||||
@node Loading
|
||||
@subsection Loading Scheme Code from File
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue