around the same time regarding a call to LIST on sparc with 1000
arguments) and other implementation limit constants.
-311: "Tokeniser not thread-safe"
- (see also Robert Marlow sbcl-help "Multi threaded read chucking a
- spak" 2004-04-19)
- The tokenizer's use of *read-buffer* and *read-buffer-length* causes
- spurious errors should two threads attempt to tokenise at the same
- time.
-
314: "LOOP :INITIALLY clauses and scope of initializers"
reported by Bruno Haible sbcl-devel "various SBCL bugs" from CLISP
test suite, originally by Thomas F. Burdick.
* bug fix: degree sign (<U00B0>) could not be encoded in KOI8-R.
* bug fix: correct pathname printing with printer escaping is on.
(thanks to Kevin Reid)
+ * threads
+ ** bug fix: release-foreground doesn't choke on session lock if
+ there is only one thread in the session
changes in sbcl-0.9.3 relative to sbcl-0.9.2:
* New feature: Experimental support for bivalent streams: streams
(defun release-foreground (&optional next)
#!+sb-doc
"Background this thread. If NEXT is supplied, arrange for it to
-have the foreground next"
+have the foreground next."
#!-sb-thread (declare (ignore next))
#!-sb-thread nil
#!+sb-thread
(with-session-lock (*session*)
- (setf (session-interactive-threads *session*)
- (delete *current-thread* (session-interactive-threads *session*)))
+ (when (rest (session-interactive-threads *session*))
+ (setf (session-interactive-threads *session*)
+ (delete *current-thread* (session-interactive-threads *session*))))
(when next
(setf (session-interactive-threads *session*)
(list* next
;;; 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.3.24"
+"0.9.3.25"