Hi Martin,
The help documentation for browser() doesn't seem to mention anywhere
that it is impossible to step outside of the function that called
browser(). Is that indeed true? Can I use the debugger effectively
without knowing it? Is there some other documentation where this fact
is mentioned?
> Frederick Eaton
> on Wed, 15 Dec 2021 20:09:46 -0800 writes:
> Just following up to check if anyone has had time to look over these
patches.
> Frederick
I strongly guess that nobody has.
Let me give you my perception of what you have tried to
propose/use, and why I hadn'
Just following up to check if anyone has had time to look over these patches.
Frederick
On Wed, Dec 08, 2021 at 12:24:47AM -0800, Frederick Eaton wrote:
Dear R Core Team,
I'm attaching a proposed patch to hopefully address my confusions regarding the
documentation of browser(). I'm not sure i
Dear R Core Team,
I'm attaching a proposed patch to hopefully address my confusions regarding the
documentation of browser(). I'm not sure if all the material I added is
correct, but I made experiments to confirm that the behavior is at least
roughly as described.
patch ./src/library/base
Dear R Devel,
I have been advised to use "options(error=recover)" to enable
debugging on errors. But sometimes it would seem more convenient to
override "stopifnot", for example:
stopifnot = function(b) { if(!b) { browser(skipCalls=1); } }
However, this doesn't do what I expected. On lookin
