From aa9a97b0a8cc052833a0015f1deebe951acf371d Mon Sep 17 00:00:00 2001 From: Nikodemus Siivola Date: Thu, 10 Mar 2005 06:01:12 +0000 Subject: [PATCH] 0.8.20.13: document current initialization file semantics --- doc/manual/start-stop.texinfo | 14 ++++++-------- version.lisp-expr | 2 +- 2 files changed, 7 insertions(+), 9 deletions(-) diff --git a/doc/manual/start-stop.texinfo b/doc/manual/start-stop.texinfo index fce6a98..f16bfca 100644 --- a/doc/manual/start-stop.texinfo +++ b/doc/manual/start-stop.texinfo @@ -243,8 +243,8 @@ This is equivalent to @code{--eval '(sb-ext:disable-debugger)'}. @comment node-name, next, previous, up @section Initialization Files -This section covers initialization files loaded at startup, which can -be used to customize the lisp environment. +This section covers initialization files processed at startup, which +can be used to customize the lisp environment. @menu * System Initialization File:: @@ -276,12 +276,10 @@ No user initialization file is required. @comment node-name, next, previous, up @subsection Initialization File Semantics -SBCL uses @code{load} to process its initialization files, which -has the unfortunate effect of preventing users from changing the -default startup @code{*package*}, and setting a default optimization -policy. - -This is considered a bug and liable to change in the future. +SBCL processes initialization files with @code{read} and @code{eval}, +not @code{load}; hence initialization files can be used to set startup +@code{*package*} and @code{*readtable*}, and for proclaiming a global +optimization policy. @node Initialization Examples @comment node-name, next, previous, up diff --git a/version.lisp-expr b/version.lisp-expr index c694d3c..cddbdfa 100644 --- 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".) -"0.8.20.12" +"0.8.20.13" -- 1.7.10.4