I think you're right, except that you don't have to manually turn on
debug when you use catchd. . If there is a catchd., debug will stay on
when you turn it on before running the code.
If you have catchd. and catch., the catch. block is ignored.
Henry Rich
On 1/12/2022 5:44 PM, Don Guinn wrote:
One last question. So, I define a catchd. block. Then it will run only if
debug is off. But if I want to see the error at the point of failure, I put
in a line to turn debug on after the try. statement. Now if I encounter an
error in that block J will stop on the line in error. It never gets a
chance to get to the catchd. block. The error would never be passed to a
catch. block either. I handle the error manually. The error is gone. So
the catchd. and/or catch. block never runs anyway as there is no longer an
error. If I have both catchd. and catch. blocks only the first block would
ever run. The second one would be useless.
What am I missing?
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
