I loved a tool STSC had for catching errors. I can't remember what it was
but it was like the ON ERROR of PLI. You could trap an error and see the
entire stack leading to the error. I have not liked the try. catch. approach
of IBM's APL2 and now in J as the catch clears the stack up to the try. So,
to find out exactly what the error is I end out with try.s all over the
place or writing out log stuff.
On Jan 29, 2008 9:14 AM, Gilles Kirouac <[EMAIL PROTECTED]> wrote:
> In thread Locale of ijx, Don Guinn wrote:
>
> > That's what I use to create the ijx window when I get an error in a
> run-only
> > application. Then it is easy to display the error information in that
> window
> > and start debugging. Beats the heck out of having to restart the
> application
> > in development mode and trying to recreate the problem.
>
> That reminds me that in some APL system, a function is available
> to save ("dump") the whole workspace including the execution stack.
> That has showed to be invaluable when my app failed in the hands
> of an end-user.
>
> I don't recall seeing that functionality provided as a library verb in J.
> I know I could roll my own. I am also aware that J can't load
> a workspace with a stack. But nevertheless a standard way would be
> useful, I believe. Have I missed it?
>
> ~ Gilles
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
