0.pre7.49:

[sbcl.git] / src / code / target-extensions.lisp

diff --git a/src/code/target-extensions.lisp b/src/code/target-extensions.lisp
index b80eb8d..7b13df4 100644 (file)
--- a/src/code/target-extensions.lisp
+++ b/src/code/target-extensions.lisp
@@ -17,19 +17,25 @@
 
 (in-package "SB!IMPL")
 \f
-;;;; miscellaneous I/O
+;;;; variables related to saving core files
+;;;;
+;;;; (Most of the save-a-core functionality is defined later, in its
+;;;; own file, but we'd like to have these symbols declared special
+;;;; and initialized ASAP.)
 
-;;; INDENTING-FURTHER is a user-level macro which may be used to locally
-;;; increment the indentation of a stream.
-(defmacro indenting-further (stream more &rest body)
+(defvar *before-save-initializations* nil
   #!+sb-doc
-  "Causes the output of the indenting Stream to indent More spaces. More is
-  evaluated twice."
-  `(unwind-protect
-     (progn
-      (incf (sb!impl::indenting-stream-indentation ,stream) ,more)
-      ,@body)
-     (decf (sb!impl::indenting-stream-indentation ,stream) ,more)))
+  "This is a list of functions which are called before creating a saved core
+  image. These functions are executed in the child process which has no ports,
+  so they cannot do anything that tries to talk to the outside world.")
+
+(defvar *after-save-initializations* nil
+  #!+sb-doc
+  "This is a list of functions which are called when a saved core image starts
+  up. The system itself should be initialized at this point, but applications
+  might not be.")
+\f
+;;;; miscellaneous I/O
 
 (defun skip-whitespace (&optional (stream *standard-input*))
   (loop (let ((char (read-char stream)))
@@ -63,29 +69,3 @@
         :format-control "~@<~A: ~2I~_~A~:>"
         :format-arguments (list prefix-string (strerror errno))
         other-condition-args))
-\f
-;;;; optimization idioms
-
-(eval-when (:compile-toplevel :load-toplevel :execute)
-
-  ;; Byte compile this thing if possible.
-  (defvar *optimize-byte-compilation*
-    '(optimize (speed 0) (safety 1)))
-
-  ;; This thing is externally visible, so compiling meta-information
-  ;; is more important than byte-compiling it; but it's otherwise
-  ;; suitable for byte-compilation.
-  ;;
-  ;; (As long as the byte compiler isn't capable of compiling
-  ;; meta-information such as the argument list required by functions
-  ;; (as in sbcl-0.6.12, anyway), it's not suitable for compiling
-  ;; externally visible things like CL:INSPECT even if their speed
-  ;; requirements are small enough that it'd otherwise be OK. If some
-  ;; later version of the byte compiler learns to compile such
-  ;; meta-information, we'll probably change the implementation of
-  ;; this idiom so that it causes byte compilation of the thing after
-  ;; all.)
-  (defvar *optimize-external-despite-byte-compilation*
-    '(optimize (speed 1)
-              ;; still might as well be as small as possible..
-              (space 3))))