eformat is tightly coupled with the interpreter, so that it can give
information at the lowest level of failure.
For calculus, you would want information at a high level. I think
try./catch. would be more appropriate.
But, if you find any way that eformat can help, you can modify the
addon. It's on GitHub. There is quite a bit of commentary in the
source that will have been stripped off in stdlib. And, if you can
think of a way JE can help, we should talk about it.
In a normal try./catch. block eformat is not run on the error. See 9!:59
if you need to change that.
Henry Rich
On 2/14/2023 8:22 AM, Jan-Pieter Jacobs wrote:
Hi,
I like the new, more explanatory error messages by dev/eformat.
A while ago, I cooked up something far more ad-hoc, and doubtlessly less
robust for the math/calculus addon, as I felt more wordy errors would help
a user better.
So now I wonder: is dev/eformat meant to (or could be extended to) allow
addon owners to define error handling for their own addons (e.g.
math/calculus)?
If already possible, how would one use eformat? I took a cursory look at
the script, but there is little information in the comments there.
Thanks,
Jan-Pieter
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
