Steel Bank Common Lisp

Update of /cvsroot/sbcl/sbcl/src/code
In directory usw-pr-cvs1:/tmp/cvs-serv1348/src/code

Modified Files:
	early-extensions.lisp host-alieneval.lisp 
	primordial-extensions.lisp 
Log Message:
0.7.3.1:
	finally getting to CLISP bootstrapping...
	...merged CSR patch "more controversial fixes" from "Re: CLISP
		compilation" sbcl-devel 2002-04-15 (which don't look
		very controversial except for the **CURRENT-SEGMENT**
		code, which is going to have to be fixed somehow and
		for which this fix looks plausible)
	...made comment fixes mostly related to CSR patch
	...fixed "#+"-should-be-"#!+" typos in parms.lisp


Index: early-extensions.lisp
===================================================================
RCS file: /cvsroot/sbcl/sbcl/src/code/early-extensions.lisp,v
retrieving revision 1.42
retrieving revision 1.43
diff -C2 -d -r1.42 -r1.43
*** early-extensions.lisp	15 Apr 2002 15:58:24 -0000	1.42
--- early-extensions.lisp	25 Apr 2002 19:26:54 -0000	1.43
***************
*** 14,29 ****
  (in-package "SB!IMPL")
  
- ;;; Lots of code wants to get to the KEYWORD package or the
- ;;; COMMON-LISP package without a lot of fuss, so we cache them in
- ;;; variables. TO DO: How much does this actually buy us? It sounds
- ;;; sensible, but I don't know for sure that it saves space or time..
- ;;; -- WHN 19990521
- ;;;
- ;;; (The initialization forms here only matter on the cross-compilation
- ;;; host; In the target SBCL, these variables are set in cold init.)
- (declaim (type package *cl-package* *keyword-package*))
- (defvar *cl-package*      (find-package "COMMON-LISP"))
- (defvar *keyword-package* (find-package "KEYWORD"))
- 
  ;;; something not EQ to anything we might legitimately READ
  (defparameter *eof-object* (make-symbol "EOF-OBJECT"))
--- 14,17 ----

Index: host-alieneval.lisp
===================================================================
RCS file: /cvsroot/sbcl/sbcl/src/code/host-alieneval.lisp,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** host-alieneval.lisp	5 Mar 2002 03:53:05 -0000	1.22
--- host-alieneval.lisp	25 Apr 2002 19:26:55 -0000	1.23
***************
*** 116,120 ****
  					   (if (atom x) x (car x)))
  					 slots)
! 			       ,@include-args)))
  	   ,@slots)))))
  
--- 116,122 ----
  					   (if (atom x) x (car x)))
  					 slots)
! 			       ,@include-args
! 			       ;; KLUDGE
! 			       &aux (alignment (or alignment (guess-alignment bits))))))
  	   ,@slots)))))
  
***************
*** 323,330 ****
  (def!struct (alien-type
  	     (:make-load-form-fun sb!kernel:just-dump-it-normally)
! 	     (:constructor make-alien-type (&key class bits alignment)))
    (class 'root :type symbol)
    (bits nil :type (or null unsigned-byte))
!   (alignment (guess-alignment bits) :type (or null unsigned-byte)))
  (def!method print-object ((type alien-type) stream)
    (print-unreadable-object (type stream :type t)
--- 325,333 ----
  (def!struct (alien-type
  	     (:make-load-form-fun sb!kernel:just-dump-it-normally)
! 	     (:constructor make-alien-type (&key class bits alignment
! 					    &aux (alignment (or alignment (guess-alignment bits))))))
    (class 'root :type symbol)
    (bits nil :type (or null unsigned-byte))
!   (alignment nil :type (or null unsigned-byte)))
  (def!method print-object ((type alien-type) stream)
    (print-unreadable-object (type stream :type t)
***************
*** 1138,1149 ****
  	     (:make-load-form-fun sb!kernel:just-dump-it-normally)
  	     (:constructor make-local-alien-info
! 			   (&key type force-to-memory-p)))
    ;; the type of the local alien
    (type (missing-arg) :type alien-type)
    ;; Must this local alien be forced into memory? Using the ADDR macro
    ;; on a local alien will set this.
!   (force-to-memory-p (or (alien-array-type-p type)
! 			 (alien-record-type-p type))
! 		     :type (member t nil)))
  (def!method print-object ((info local-alien-info) stream)
    (print-unreadable-object (info stream :type t)
--- 1141,1153 ----
  	     (:make-load-form-fun sb!kernel:just-dump-it-normally)
  	     (:constructor make-local-alien-info
! 			   (&key type force-to-memory-p
! 			    &aux (force-to-memory-p (or force-to-memory-p
! 							(alien-array-type-p type)
! 							(alien-record-type-p type))))))
    ;; the type of the local alien
    (type (missing-arg) :type alien-type)
    ;; Must this local alien be forced into memory? Using the ADDR macro
    ;; on a local alien will set this.
!   (force-to-memory-p nil :type (member t nil)))
  (def!method print-object ((info local-alien-info) stream)
    (print-unreadable-object (info stream :type t)

Index: primordial-extensions.lisp
===================================================================
RCS file: /cvsroot/sbcl/sbcl/src/code/primordial-extensions.lisp,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** primordial-extensions.lisp	15 Jan 2002 23:53:51 -0000	1.18
--- primordial-extensions.lisp	25 Apr 2002 19:26:55 -0000	1.19
***************
*** 134,137 ****
--- 134,149 ----
  ;;;; miscellany
  
+ ;;; Lots of code wants to get to the KEYWORD package or the
+ ;;; COMMON-LISP package without a lot of fuss, so we cache them in
+ ;;; variables. TO DO: How much does this actually buy us? It sounds
+ ;;; sensible, but I don't know for sure that it saves space or time..
+ ;;; -- WHN 19990521
+ ;;;
+ ;;; (The initialization forms here only matter on the cross-compilation
+ ;;; host; In the target SBCL, these variables are set in cold init.)
+ (declaim (type package *cl-package* *keyword-package*))
+ (defvar *cl-package*      (find-package "COMMON-LISP"))
+ (defvar *keyword-package* (find-package "KEYWORD"))
+ 
  ;;; Concatenate together the names of some strings and symbols,
  ;;; producing a symbol in the current package.