[Sbcl-commits] CVS: sbcl NEWS, 1.1493, 1.1494 version.lisp-expr, 1.4384, 1.4385

[Richard M K. <kr...@us...>]

Update of /cvsroot/sbcl/sbcl
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv19898

Modified Files:
	NEWS version.lisp-expr 
Log Message:
1.0.27.18: Changes to ECHO-STREAMs

* Bugfix: PEEK-CHAR always popped the unread-stuff, leading to
  spurious duplicate echos in some cases.

* Minor incompatible change: UNREAD-CHAR on an ECHO-STREAM now unreads
  onto the echo-stream's input stream.  This is unspecified in the
  CLHS, but makes SBCL compatible with most implementations (AFAICT,
  everybody but CMUCL).

* Minor incompatible change: echo-streams used to buffer arbitrarily
  many characters in UNREAD-CHAR.  Conforming programs can't have
  relied on this, but non-conforming ones might have; users who need
  the old CMUCL/SBCL behavior can do it easily and de-facto-portably
  with Gray Streams.

* Possible bugfix that nobody cares about: ECHO-N-BIN (which
  implements a path through READ-SEQUENCE) can never have worked after
  an UNREAD-CHAR, because it tried to store characters into an octet
  buffer.


Index: NEWS
===================================================================
RCS file: /cvsroot/sbcl/sbcl/NEWS,v
retrieving revision 1.1493
retrieving revision 1.1494
diff -u -d -r1.1493 -r1.1494
--- NEWS	21 Apr 2009 11:33:38 -0000	1.1493
+++ NEWS	22 Apr 2009 15:42:41 -0000	1.1494
@@ -8,6 +8,9 @@
   * improvement: on x86/x86-64 Lisp call frames now have the same layout as C
     frames, allowing for instance more reliable backtraces.
   * optimization: faster local calls on x86/x86-64
+  * minor incompatible changes: echo-streams now propagate unread-char to the
+    underlying input stream, and no longer permit unreading more than one
+    character.
 
 changes in sbcl-1.0.27 relative to 1.0.26:
   * new port: support added for x86-64 OpenBSD. (thanks to Josh Elsasser)

Index: version.lisp-expr
===================================================================
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.4384
retrieving revision 1.4385
diff -u -d -r1.4384 -r1.4385
--- version.lisp-expr	21 Apr 2009 11:33:38 -0000	1.4384
+++ version.lisp-expr	22 Apr 2009 15:42:41 -0000	1.4385
@@ -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.27.17"
+"1.0.27.18"