1.0.43.18: index SB-EXT:*EVALUATOR-MODE* under #'EVAL in the manual

 Looking for "Interpreter" in the concept index isn't probably the
 first thing most people do.

 Fixes the documentation half of lp#654289.

diff --git a/doc/manual/compiler.texinfo b/doc/manual/compiler.texinfo
index f90f972..5fa6525 100644 (file)
--- a/doc/manual/compiler.texinfo
+++ b/doc/manual/compiler.texinfo
@@ -1114,15 +1114,15 @@ a more efficient calling convention that forbids redefinition.
 @comment  node-name,  next,  previous,  up
 @section Interpreter
 @cindex Interpreter
+@findex @cl{eval}
 @vindex @sbext{@earmuffs{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}.
+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.
+
+@include var-sb-ext-star-evaluator-mode-star.texinfo

diff --git a/version.lisp-expr b/version.lisp-expr
index dea8905..a4ed179 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.43.17"
+"1.0.43.18"