[Octave-bug-tracker] [bug #46795] dbstop lacks much Matlab functionality

[Lachlan Andrew]

Follow-up Comment #3, bug #46795 (project octave):

Thanks for your helpful feedback, Philip.

You are right that "dbstop in ... if ..." is not very useful without an "at
<line>".  I was toying with the idea of allowing the condition to be evaluated
in the *caller's* scope instead of the function's scope, perhaps with a syntax
like


dbstop in <function> if ../(iter==3)


(Mixing variables from different scopes may be nice, but would mess with the
parser too much.) However, I was hoping to have a patch that fixes
compatibility separately from one that extends functionality.  Also on my list
of extensions is "dbstop once", which would clear the breakpoint as soon as it
has been triggered, to allow "stepping" through the code in big chunks, such
as stepping over a loop.

I agree that the scrolling is annoying.  It is the behaviour of existing code,
so I'll try to create a separate patch for that, though I have no idea how
yet.  I don't think it needs a separate bug report, but that's your call.

The issue of asking to restore breakpoints is again someone else's code.  My
preference would be always to save and restore breakpoints, and never ask. 
That will save a little code bloat.  Can you think of any reason someone would
not want to restore the breakpoints, given they can just click a button to
clear all breakpoints anyway?  If so, I'll just make save-without-asking the
default an keep the code to allow it to be changed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46795>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/