Richard Fateman wrote:
> Raymond Toy wrote:
>> This seems nice. But what would be nicer than having the program stop
>> (as we can with Maxima) exactly at the point of the error so we can
>> debug it?
> Sometimes. You are assuming that the person running the program is
> also the person who wrote the
> program or is capable of debugging it. A successful program
> presumably is run by other people.
> Of course such a program should not produce errors :)
Yes, but even if the user can't debug it, there can be useful
information that would let someone else be able to debug it.
I almost always run maxima with the -g option so that Lisp errors don't
just throw to the top-level.
Perhaps we can make these signal errors that are handled to return
NoObject things, but users/developers can make it so that the error is
actually caught and throws the user to the debugger?
I've found it quite useful to have debugmode(true) when trying to figure
out where my maxima routine was dividing by zero. It's really annoying
to have some long running routine stop with a divide by zero error and
no way of figuring out where that happened.
Ray