|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #55599] print_usage() within subfunction results error |
Date: | Thu, 7 Feb 2019 11:57:06 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #5, bug #55599 (project octave): Maybe it would make sense for print_usage to be a built-in function so that it could easily find the parent calling function from the call stack. Or, to provide sufficient access to the call stack and/or info about the currently executing function (not just in the form currently provided by dbstack) to allow print_usage to remain a .m file but to find the ultimate parent function. Then we could continue to write "print_usage()" in sub or nested functions and automatically find the doc string of the parent. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55599> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |