X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fmanual%2Fcompiler.texinfo;h=d2d9746082bf1fdf53cc7318b93a5845683d4ed6;hb=031646c3b8236eb441434664e10fb88f8e7ec7be;hp=729865fb7eb7bf6c086cbdeb51947cfc49402370;hpb=58ef9d8996d4421610101b52e5a25fd2c70c4792;p=sbcl.git diff --git a/doc/manual/compiler.texinfo b/doc/manual/compiler.texinfo index 729865f..d2d9746 100644 --- a/doc/manual/compiler.texinfo +++ b/doc/manual/compiler.texinfo @@ -16,6 +16,7 @@ separate that they have their own chapter, @ref{Efficiency}. * Compiler Policy:: * Compiler Errors:: * Open Coding and Inline Expansion:: +* Interpreter:: @end menu @node Diagnostic Messages @@ -514,14 +515,16 @@ selectable via @code{optimize} declarations. All declarations are considered assertions to be checked at runtime, and all type checks are precise. -Used when @code{(>= safety (max speed space compilation-speed)}. The +Used when @code{(and (< 0 safety) (or (>= safety 2) (>= safety speed)))}. The default compilation policy provides full type checks. @item Weak Type Checks Any or all type declarations may be believed without runtime -assertions, and assertions that are done may be imprecise. +assertions, and assertions that are done may be imprecise. It should +be noted that it is relatively easy to corrupt the heap when weak type +checks are used, and type-errors are introduced into the program. -Used when @code{(< 0 safety (max speed space compilation-speed)}. +Used when @code{(and (< safety 2) (< safety speed))} @item No Type Checks All declarations are believed without assertions. Also disables @@ -1088,3 +1091,20 @@ open-coded. Even when not open-coded, a call to a standard function may be transformed into a different function call (as in the last example) or compiled as @emph{static call}. Static function call uses a more efficient calling convention that forbids redefinition. + +@node Interpreter +@comment node-name, next, previous, up +@section Interpreter +@cindex Interpreter +@vindex sb-ext:*evaluator-mode* + +By default SBCL implements @code{eval} by calling the native code +compiler. SBCL also includes an interpreter for use in special cases +where using the compiler is undesirable, for example due to compilation +overhead. Unlike in some other Lisp implementations, in SBCL interpreted +code is not safer or more debuggable than compiled code. + +Switching between the compiler and the interpreter is done using the +special variable @code{sb-ext:*evaluator-mode*}. As of 0.9.17, valid +values for @code{sb-ext:*evaluator-mode*} are @code{:compile} and +@code{:interpret}.