Home > Archive > APL > November 2004 > "Re: Any suggestion for this error trapping problem?"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
"Re: Any suggestion for this error trapping problem?"
|
|
|
| I'm running APL programs all day every 60 seconds during the
w . The nature of the information being generated is not
so time sensitive that it would hurt the operation to simply
branch out of a program when errors occur. The alternative
is the operation stops running until I notice the problem.
I need an error trapping solution that branches out of the
primary function being run - since the next run will provide
similar information. If I just branch out of the immediate
function another error might occur due to a difference in
the size of matrices being generated another issue.
I've looked utility workspace in an APL2000 version at a
function called GOTO but I'm not sure if this or some other
function would provide a better generalized solution for
the error trapping problem I've described. Any ideas?
Harry
| |
| Eric Landau 2004-11-17, 3:56 pm |
| In article <e60dcbb6.0411170437.61551f13@posting.google.com>,
aplisfast@yahoo.com (Harry) wrote:
>I'm running APL programs all day every 60 seconds during the
>w . The nature of the information being generated is not
>so time sensitive that it would hurt the operation to simply
>branch out of a program when errors occur. The alternative
>is the operation stops running until I notice the problem.
>
>I need an error trapping solution that branches out of the
>primary function being run - since the next run will provide
>similar information. If I just branch out of the immediate
>function another error might occur due to a difference in
>the size of matrices being generated another issue.
>
>I've looked utility workspace in an APL2000 version at a
>function called GOTO but I'm not sure if this or some other
>function would provide a better generalized solution for
>the error trapping problem I've described. Any ideas?
Take a look at the HANDLERS workspace in the TOOLS library distributed
with the APL2000 Windows interpreter.
Eric Landau, APL Solutions, Inc.
"Sacred cows make the tastiest hamburger." - Abbie Hoffman
| |
|
| I've looked at the workspace which is not very well documented.
It may be adequate for those familar with error trapping functions
but otherwise lacks details.
Does anyone have examples? If so I would appreciate hearing from
you either via email, in this group or both.
elandau@cais.com (Eric Landau) wrote in message news:<n6mdndB64aR00AbcRVn-sA@rcn.net>...
> In article <e60dcbb6.0411170437.61551f13@posting.google.com>,
> aplisfast@yahoo.com (Harry) wrote:
>
>
> Take a look at the HANDLERS workspace in the TOOLS library distributed
> with the APL2000 Windows interpreter.
>
> Eric Landau, APL Solutions, Inc.
> "Sacred cows make the tastiest hamburger." - Abbie Hoffman
| |
| Eric Landau 2004-11-18, 3:56 pm |
| In article <e60dcbb6.0411180450.2efa19b8@posting.google.com>,
aplisfast@yahoo.com (Harry) wrote:
[color=darkred]
>I've looked at the workspace which is not very well documented.
>It may be adequate for those familar with error trapping functions
>but otherwise lacks details.
>
>Does anyone have examples? If so I would appreciate hearing from
>you either via email, in this group or both.
>
>elandau@cais.com (Eric Landau) wrote in message
> news:<n6mdndB64aR00AbcRVn-sA@rcn.net>...
>
There is good documentation in the original APL*Plus III User Manual
from Manugistics (APL*Plus III was acquired from Manugistics by APL2000
and renamed APL+Win): an 8-page discussion of "Using the HANDLERS
Workspace", with examples, that starts on p.8-11. I do not know if this
has been reprinted in any of the documentation issued by APL2000, but it
probably has.
Eric Landau, APL Solutions, Inc.
"Sacred cows make the tastiest hamburger." - Abbie Hoffman
| |
|
| Eric, thanks for your comments. Apparently, a global solution to
branch out of all functions regardless of the source of the error
-- into an error free workspace is more complex than I thought.
I no longer have my APL*Plus III manuals but I know someone who
might -- so I'm getting closer to a solution.
elandau@cais.com (Eric Landau) wrote in message news:<rt6dnXc6OKmWOwHcRVn-jw@rcn.net>...
> In article <e60dcbb6.0411180450.2efa19b8@posting.google.com>,
> aplisfast@yahoo.com (Harry) wrote:
>
>
> There is good documentation in the original APL*Plus III User Manual
> from Manugistics (APL*Plus III was acquired from Manugistics by APL2000
> and renamed APL+Win): an 8-page discussion of "Using the HANDLERS
> Workspace", with examples, that starts on p.8-11. I do not know if this
> has been reprinted in any of the documentation issued by APL2000, but it
> probably has.
>
>
> Eric Landau, APL Solutions, Inc.
> "Sacred cows make the tastiest hamburger." - Abbie Hoffman
|
|
|
|
|