Cleanup.
* Fix formatting of sub-items in 0.9.17 NEWS (thanks to Kevin Reid)
* gc.lisp whitespace canonicalization
* bug fix: SLOT-VALUE optimizations are no longer done on method parameters
whose bindings are modified
* improvements to the win32 port (thanks to Yaroslav Kavenchuk):
- * bug fix: arguments to RUN-PROGRAM are escaped correctly
- * replace dummy implementations of CL:MACHINE-INSTANCE and
- CL:SOFTWARE-VERSION with proper version
+ ** bug fix: arguments to RUN-PROGRAM are escaped correctly
+ ** replace dummy implementations of CL:MACHINE-INSTANCE and
+ CL:SOFTWARE-VERSION with proper version
changes in sbcl-0.9.16 relative to sbcl-0.9.15:
* feature: implemented the READER-METHOD-CLASS and
(sb!thread:make-mutex :name "GC lock") "ID of thread running SUB-GC")
(defun sub-gc (&key (gen 0))
- (unless (eq sb!thread:*current-thread*
+ (unless (eq sb!thread:*current-thread*
(sb!thread::mutex-value *already-in-gc*))
;; With gencgc, unless *GC-PENDING* every allocation in this
;; function triggers another gc, potentially exceeding maximum
;; from the outermost SUB-GC?
;;
;; KLUDGE: Don't run the hooks in GC's triggered by dying threads,
- ;; so that user-code never runs with
+ ;; so that user-code never runs with
;; (thread-alive-p *current-thread*) => nil
;; The long-term solution will be to keep a separate thread for
;; finalizers and after-gc hooks.
;;; 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.9.17.5"
+"0.9.17.6"