Eh... and I still managed to get it wrong, here...
Maybe setting stops gave that behavior, but reviewing
https://github.com/jsoftware/j-playground/issues/31 I see that it was
stopping from an error (as opposed to an explicit stop -- I don't know
if those were ever enabled).
We can still lock up
In my last report on the J Wiki Meeting of July 7th, I incorrectly stated that
Raul through that recursive debugging calls may be problematic. He contacted me
with the following information to set the record straight:
Raul: The issue I was thinking about was where it used to be that hitting a
My work testing J Playground led me to want debugging tools, so I've written
an adverb. You invoke it with:
]debug
It sets up debugging and takes over immediate execution with ". as its
argument.
Together with u. it can access your local names.
Thanks to JoeBo, an early version of my efforts
