Even with emphasis, I can't say I'm 100% sure what that sentence says.
It means just what Roger chose it to mean, neither more nor less.
I am looking for comments on whether the current behavior is desirable.
Henry Rich
On 4/6/2022 7:33 PM, Elijah Stone wrote:
Haven't used the debugger extensively and haven't used dbcut. That said:
1. If you change some global state first, perhaps the code will start
working
2. The dictionary says (emphasis mine):
Cut back one stack level, _stopping_ at the line at the next stack level
-E
On Wed, 6 Apr 2022, Henry Rich wrote:
dbcut (13!:19) seems to go up one stack level and immediately
reexecute the line that failed. Huh?
Unless you have a stop on that line, you will rerun it and it will
fail again. If you do have a stop on the line, the reexecution is
nugatory.
Can anyone suggest a reason why 'cut back' should not just cut the
stack back and remain in suspension?
[It is possible that I have read the code wrong.]
Henry Rich
--
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
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
