[Rd] debugonce() functions are not considered as debugged

[Gábor Csárdi]

On Mon, May 21, 2018 at 5:01 PM Tomas Kalibera <tomas.kalibera at gmail.com>
wrote:
[...]
> Do you have a good use case when it would be useful to query/unset the
> mark for debugonce?

Well, I suppose the same use cases when it is useful to query/unset the
other debug
mark.

To be more specific, in debug helpers for a tool that works with callbacks
from a central event loop, it is nice to be able to tell which callbacks are
"debugged" currently, either via `debug()` or  `debugonce()`.

Gabor

> Best,
> Tomas

> On 04/28/2018 01:57 PM, Gábor Csárdi wrote:
> > debugonce() sets a different flag (RSTEP), and this is not queried by
> > isdebugged(), and it is also not unset by undebug().
> >
> > Is this expected? If yes, is there a way to query and unset the RSTEP
flag
> > from R code?
> >
> > ❯ f <- function() { }
> > ❯ debugonce(f)
> > ❯ isdebugged(f)
> > [1] FALSE
> >
> > ❯ undebug(f)
> > Warning message:
> > In undebug(f) : argument is not being debugged
> >
> > ❯ f()
> > debugging in: f()
> > debug at #1: {
> > }
> > Browse[2]>
> >
> > ______________________________________________
> > R-devel at r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel