On Wed, Apr 13, 2022 at 12:28 PM 'Pascal Jasmin' via Beta <[email protected]> wrote: > Sure, being able to inspect variables after a jbreak can be useful. But > there's only 2 reasons to call jbreak. An infinite loop bug, or "it's just > taking longer than I wanted to wait". The line of code where jbreak occurred > tells you both problems. The 2nd reason for jbreak, if the code is fine, is > that the input was too large/"permutationy"
There's also sometimes a need to inspect intermediate results. Here, it's nice if the code can be restarted. Also, it's probably worth noting that the way we deal with race conditions is by designing our code so that we can recover from the races. I imagine this as one of the motivations for functional programming. But other approaches also work, as long as you have useful atomic operations which you understand. Anyways.. we should expect that jbreak could increase the magnitude of race conditions. So, it should also be useful in our attempts to locate them. Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
