[Octave-bug-tracker] [bug #60466] Wish: errors in built-in functions should provide debugging information pointing to m-file context

[Nicholas Jankowski]

Follow-up Comment #5, bug #60466 (project octave):

adding (as mentioned over in bug #60264) that classes (classdef and old
@style) also produce this same behavior, with the added caveat that the error
stack also neglects to tell you what class the function/method belonged to. 

is this request sufficiently distinct from bug #60264 to keep both open? 


    _______________________________________________________

Reply to this item at:

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

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