You can cut & resume by doing cut followed by run.
I'm not much of a debugger user... what good is Cut Stack if you hit an
error? When you restart you'll hit the error again, right? If you Cut
Stack after a stop, that's different.
I'm thinking that if the suspension happened because of an error, the
Cut Stack should give the value to use for the result; otherwise a
special error should be raised to cause the sentence to abort quietly
and then suspend. That's almost compatible with what we have now, the
difference being that dbcut'' would use a result value of (i. 0) rather
than (i. 0 0).
Henry Rich
On 7/2/2022 7:06 PM, Raul Miller wrote:
On Sat, Jul 2, 2022 at 5:46 PM Henry Rich <henryhr...@gmail.com> wrote:
It's not really a matter of workload. There may be users who have
gotten used to the current behavior, which more often than not is OK,
and I don't want to surprise them without good cause.
I think what we are seeing here is leftovers from the days when we
hoped we could leave stops in the middle of tacit expressions.
That said, I suppose it might make sense to have both "cut back the
stack and resume debugging" and a "cut back the stack and resume
execution" operations.
--
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
