[Octave-bug-tracker] [bug #55599] print_usage() within subfunction results error

[Rik]

Follow-up Comment #6, bug #55599 (project octave):

I could see making print_usage automatically work its way up to the parent
function.  But, there's probably other things I'd work on first.  In this
case, it doesn't seem that hard to provide the name of the parent function
when writing the subfunctions and nested functions.

If you want a generic m-file solution you can write


    print_usage (mfilename ());


rather than, say,



    print_usage ("gradient");




    _______________________________________________________

Reply to this item at:

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

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