use debugger loop instead of break loop in BREAK ?

Hello,

In exploring the debugger and related stuff in Maxima,
I see that there is one kind of prompt (supplied by
BREAK-DBM-LOOP in mdebug.lisp) for the debugger and 
another prompt (supplied by MBREAK-LOOP in macsys.lisp)
for the BREAK command.
 
I'd like to suggest that the call to MBREAK-LOOP be 
replaced by a call to BREAK-DBM-LOOP. I've done this in
my copy (cvs version of 2003 11 28) and it works as
expected, although the :next and :step commands just
keep going instead of stepping -- doubtless this is 
because I supplied nil (no "where am I" information) 
to BREAK-DBM-LOOP. Here is the patch:

--- macsys.lisp 20 Nov 2003 13:01:51 -0000      1.24
+++ macsys.lisp 17 Dec 2003 04:43:58 -0000
@@ -242,5 +242,5 @@
 (DEFUN $BREAK (&REST ARG-LIST)
   (PROG1 (apply #'$PRINT ARG-LIST)
-        (MBREAK-LOOP)))
+        (break-dbm-loop nil)))


MBREAK-LOOP doesn't do anything special, so in replacing
it, there is no lost functionality. BREAK-DBM-LOOP does a
little bit more -- it understands the :foobar commands;
MBREAK-LOOP doesn't.

The advantage of using the debugger prompt in BREAK is that
it will be more comprehensible for the user -- at present
there are several operating modes (Maxima prompt, 
debugger, BREAK, and Lisp) and we may want to reduce this
embarassment of riches.

For what it's worth,
Robert Dodier


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/