I wonder what would the restored state be like when there are open windows,
files, network connections, DLL handles, and other system resources.
A way to diagnose effectively is to have well-instrumented code.
It will then just tell you what's wrong.
JAL Package Manager is a good example, considering how easy it was to locate
the 64 bit compatibility issue.
Oleg
On Jan 29, 2008, at 11:14, "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
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
