single jbreak makes the next line fail with the 'attention interrupt'
error, as if it had executed. This is seen by all tasks. This error is
handled in the catch.; if there is a task without catch., it will (1)
turn the error into break, stopping all threads, if debug is off; (2) go
into debug suspension, if debug is on.
A second jbreak would fail everything with 'break' error.
Henry Rich
On 4/14/2022 1:21 PM, Raul Miller wrote:
How is try/catch handled, in this context?
For example:
routine=: {{
try.
6!:3 y
'done'
catch.
'caught'
end.
}}
routine 5 NB. then run jbreak once:
caught
Thanks,
--
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
