* don't use PREPROCESS-FOR-EVAL for EVAL in the debugger since
the documentation was just updated to that effect, and it
takes two arguments anyways. Restoring this as part of the
debugger command loop might be nice, but potentially confusing.
(t
(funcall cmd-fun))))))))))))
-;;; FIXME: We could probably use INTERACTIVE-EVAL for much of this logic.
(defun debug-eval-print (expr)
(/noshow "entering DEBUG-EVAL-PRINT" expr)
- (let ((values (multiple-value-list
- (interactive-eval (sb!di:preprocess-for-eval expr)))))
+ (let ((values (multiple-value-list (interactive-eval expr))))
(/noshow "done with EVAL in DEBUG-EVAL-PRINT")
(dolist (value values)
(fresh-line *debug-io*)
;;; 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.20.2"
+"0.8.20.3"