|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #55178] Improved debug on error behaviour inside octave core functions |
Date: | Mon, 8 Nov 2021 10:41:39 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36 Edg/95.0.1020.40 |
Follow-up Comment #9, bug #55178 (project octave): Imho, it would be confusing if the `error` function would behave differently depending of in which function it is called. At the moment its behavior is pretty clear and makes sense to me: The error stack is from where the `error` function is called. Maybe some kind of code analysis tool could point to a probable cause of an error. I guess that is what you are interested in? If you'd like to implement a (static) code analyzer for Octave, please give it a try. Some time ago, someone mentioned adding a GUI element that would allow an easy traversal of the error stack. Maybe that would somewhat alleviate this issue. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55178> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |