[Octave-bug-tracker] [bug #55178] Improved debug on error behaviour inside octave core functions

[Kai Torben Ohlhus]

Follow-up Comment #10, bug #55178 (project octave):

@gwiora: Thanks for the example in file #52223) comment #6 🙂👍

>From a user perspective the point where the debugger stops does not make super
much sense in my opinion either.

However, you would only stop in "print_usage" when you really screwed up a
function call (which is most likely only once during the early development
stage of a function).

Thus it might be an item, "not annoying enough" to care about.  The casual
Octave user might be unaffected, as they do not user "debug_on_error" by
default.  At lease I did not stumble over this very often 😇

By the current design of "print_usage" as m-file, I do not see much potential
for improving the situation easily.

Something like "evalin ('caller', 'error (...)')" will not work.

I see the original idea of this function: something like "error", but with an
automatic descriptive message provided by the calling functions doc string.

Maybe you can start by refactoring "print_usage" in C++ by looking at error()

https://hg.savannah.gnu.org/hgweb/octave/file/cf434923aec0/libinterp/corefcn/error.cc#l1177

and change the way the error message is created.

Are you interested in workin on this? 🙂

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55178>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/