X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fcross-misc.lisp;h=7a4152edab5777a63c180613c7e73ed58fed6b23;hb=5edd74f6911093805a009a152b32216b3dba59f7;hp=6c3b8ceabc817956a07bb7678b6433e7aec860d8;hpb=cea4896b2482b7b2b429c1631d774b4cfbc0efba;p=sbcl.git

diff --git a/src/code/cross-misc.lisp b/src/code/cross-misc.lisp
index 6c3b8ce..7a4152e 100644
--- a/src/code/cross-misc.lisp
+++ b/src/code/cross-misc.lisp
@@ -32,15 +32,6 @@
   `(progn ,@forms))
 
 ;;; When we're running as a cross-compiler in an arbitrary host ANSI
-;;; Lisp, we don't have any hooks available to manipulate the
-;;; debugging name and debugging argument list of an interpreted
-;;; function object (and don't care much about getting debugging name
-;;; and debugging argument list right anyway).
-(defun try-to-rename-interpreted-function-as-macro (f name lambda-list)
-  (declare (ignore f name lambda-list))
-  (values))
-
-;;; When we're running as a cross-compiler in an arbitrary host ANSI
 ;;; Lisp, we shouldn't be doing anything which is sensitive to GC.
 ;;; KLUDGE: I (WHN 19990131) think the proper long-term solution would
 ;;; be to remove any operations from cross-compiler source files
@@ -50,10 +41,10 @@
 (defvar *after-gc-hooks* nil)
 
 ;;; The GENESIS function works with fasl code which would, in the
-;;; target SBCL, work on LISP-STREAMs. A true LISP-STREAM doesn't seem
-;;; to be a meaningful concept in ANSI Common Lisp, but we can fake it
-;;; acceptably well using a standard STREAM.
-(deftype lisp-stream () 'stream)
+;;; target SBCL, work on ANSI-STREAMs (streams which aren't extended
+;;; Gray streams). In ANSI Common Lisp, an ANSI-STREAM is just a
+;;; CL:STREAM.
+(deftype ansi-stream () 'stream)
 
 ;;; In the target SBCL, the INSTANCE type refers to a base
 ;;; implementation for compound types. There's no way to express
@@ -82,7 +73,7 @@
   (and (typep x 'simple-array)
        (= 1 (array-rank x))))
 
-;;; Genesis needs these at cross-compile time. The target
+;;; GENESIS needs these at cross-compile time. The target
 ;;; implementation of these is reasonably efficient by virtue of its
 ;;; ability to peek into the internals of the package implementation;
 ;;; this reimplementation is portable but slow.