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

[Georg Wiora]

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

Thanks for asking me to contribute actively. My involvement and my energy
budget does not allow me to enter this project in an active role. I can
contribute on the level I did and give something back to this great project
that really improves my work, but not more. Sorry for that.

I was inspired to this proposal by the way matlab does handle errors in core
functions and in packet functions: The error message is issued on the line the
user code calls the code function and not inside the method. This really
improves the development process. And in my experience these kind of errors do
not only occur in the early development stage but also during interactive
development/debugging and data analysis. This is maybe the most annoying case,
because while stopped at a break point, a wrong command call on the command
line brings the debugger in an unwanted stack position. I have to dbup until I
get back to my original position and can try again with the correct command.

I understand that there are different possibilities in the rating of this
proposal. It may not be the most important improvement, but for me it would
resolve a source of permanent annoyance during octave code development. Thanks
for your support.

    _______________________________________________________

Reply to this item at:

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

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