diff options
author | Christophe Rhodes <csr21@cantab.net> | 2009-03-01 21:49:12 +0000 |
---|---|---|
committer | Christophe Rhodes <csr21@cantab.net> | 2009-03-01 21:49:12 +0000 |
commit | fdb3f2944f1dbfdfb6e4bbba6dd2ed0da7c6a31d (patch) | |
tree | 8afd48167d80f66a9ed7573505a3ff8d1b1c9cf2 | |
parent | dd65639fb561a1cac59f5b0dc03482b8adb5441e (diff) |
1.0.26: release, will be tagged as sbcl_1_0_26sbcl_1_0_26
-rw-r--r-- | NEWS | 6 | ||||
-rw-r--r-- | version.lisp-expr | 2 |
2 files changed, 4 insertions, 4 deletions
@@ -1,14 +1,14 @@ ;;;; -*- coding: utf-8; fill-column: 78 -*- changes in sbcl-1.0.26 relative to 1.0.25: - * incompatible change: the interruption (be it a function passed to + * incompatible change: an interruption (be it a function passed to INTERRUPT-THREAD or a timer function) runs in an environment where interrupts can be enabled. The interruption can use WITH-INTERRUPTS or WITHOUT-INTERRUPTS as it sees fit. Use WITHOUT-INTERRUPTS to avoid nesting of interruptions and - potentially running out of stack. Keep in mind that in the absance + potentially running out of stack. Keep in mind that in the absence of WITHOUT-INTERRUPTS some potentially blocking operation such as acquiring a lock can enable interrupts. - * incompatible change: GC-OFF and GC-ON are removed, they were + * incompatible change: GC-OFF and GC-ON are removed, as they were always unsafe. Use WITHOUT-GCING instead. * new feature: runtime option --disable-ldb * new feature: runtime option --lose-on-corruption to die at the diff --git a/version.lisp-expr b/version.lisp-expr index ebeb71145..c3731e892 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -17,4 +17,4 @@ ;;; 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".) -"1.0.25.58" +"1.0.26" |