From 5908c8d60e19853f08416a1660f753c65caeb520 Mon Sep 17 00:00:00 2001 From: Nikodemus Siivola Date: Wed, 2 Mar 2005 06:45:47 +0000 Subject: [PATCH] 0.8.20.3: unbreak debugger * 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. --- src/code/debug.lisp | 4 +--- version.lisp-expr | 2 +- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/src/code/debug.lisp b/src/code/debug.lisp index 9072166..5707e28 100644 --- a/src/code/debug.lisp +++ b/src/code/debug.lisp @@ -741,11 +741,9 @@ reset to ~S." (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*) diff --git a/version.lisp-expr b/version.lisp-expr index 2008491..009f21b 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".) -"0.8.20.2" +"0.8.20.3" -- 1.7.10.4