0.8.6.34:

	Am I the only one who screws up in amusing ways?
	... define a fake %READER-ERROR on the host, so that planting
		commas in code which doesn't want them gives you an
		error message that's applicable, not an undefined function
		error.

diff --git a/src/code/backq.lisp b/src/code/backq.lisp
index 8393141..b82b464 100644 (file)
--- a/src/code/backq.lisp
+++ b/src/code/backq.lisp
@@ -249,4 +249,12 @@
   '(backq-comma backq-comma-at backq-comma-dot backq-list
     backq-list* backq-append backq-nconc backq-cons backq-vector))
 
+;;; Since our backquote is installed on the host lisp, and since
+;;; developers make mistakes with backquotes and commas too, let's
+;;; ensure that we can report errors rather than get an undefined
+;;; function condition on %READER-ERROR.
+#+sb-xc-host ; proper definition happens for the target
+(defun %reader-error (stream format-string &rest format-args)
+  (bug "READER-ERROR on stream ~S: ~?" stream format-string format-args))
+
 (/show0 "done with backq.lisp")

diff --git a/version.lisp-expr b/version.lisp-expr
index 212ebf9..3ae3ac7 100644 (file)
--- 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".)
-"0.8.6.33"
+"0.8.6.34"