Responding to jbreak still needs to be designed.  Currently it will interrupt only the first thread that sees it.  That seems wrong.  How should it work?

Don't draw too many conclusions from the behavior of beta-a in edge cases.

Henry Rich

On 4/13/2022 9:42 AM, Raul Miller wrote:
On Wed, Apr 13, 2022 at 8:46 AM Henry Rich <[email protected]> wrote:
I don't think this is a deadlock.  It's just an infinite recursion, made
painfully slow by the delay.
In my case, it was the script I had sent you that was hanging, and was
not (after a few seconds, or a few hours) interruptible.

Shouldn't it at least be interruptible?

Thanks,


--
Raul
----------------------------------------------------------------------
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

Reply via email to