search for: debugonce

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:...

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()` o...

On 05/22/2018 06:07 PM, G?bor Cs?rdi wrote: > 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. I asked because the use cases for undebug/debugonce I can think of do not apply. undebug() is needed once you have run a function through a debugger few times and figured out there is no bug...

...re that whenever "fun" is called, the debugger is entered undebug(fun) removes this mark; it won't stop any current debugging of that function isdebugged(fun) tells whether this mark is set or not; it does not tell whether "fun" is currently running in a debugger/browser debugonce(func) adds a different mark to the function, one that makes sure the first time "fun" is called, the debugger is entered; this is the same as when entering that function via "s" while debugging its caller. There is no way to query or unset this mark. Do you have a good use c...

...t; >> What would you want? Probably the latter, right? >> With my use case below, however, I could argue I'd even want browser() >> to be a no-op in that case. It is not so important to me. >> >> > What is the effect of a call to a function marked with debugOnce()? >> >> Good question. Here my code was such that the function would also >> not have been debugged. >> But of course, that is open for "debate", and I am glad you've >> started / continued the discussion. >> >> My main use case fo...

But the main point is where arguments are mixed together: > debugonce(plot.default) > plot(x=1:10, y=, 'l') ... Browse[2]> missing(y) [1] FALSE Browse[2]> y [1] "l" Browse[2]> type [1] "p" I think that's what I fall over mostly: that named, empty arguments behave entirely different from omitting them (", ,") And...

...that case effectively means "dropped" as we have seen in the examples. > On Fri, Nov 30, 2018 at 8:18 AM Emil Bode <emil.bode at dans.knaw.nl> wrote: >> >> But the main point is where arguments are mixed together: >> >> > debugonce(plot.default) >> > plot(x=1:10, y=, 'l') >> ... >> Browse[2]> missing(y) >> [1] FALSE >> Browse[2]> y >> [1] "l" >> Browse[2]> type >> [1] "p" >> >> I think t...

Dear R-Devel, I seem to no longer be able to access the bug-reporting system, so am doing this by e-mail. My report concerns models where variables are explicitly referenced (or is it "dereferenced"?), such as: cars.lm <- lm(mtcars[[1]] ~ factor(mtcars$cyl) + mtcars[["disp"]]) I have found that it is not possible to predict such models with new data. For example:

...> which is not quite a "vanilla repr.ex." in my view > > Worse, I cannot reproduce : > > > Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") > > Sys.getenv("_R_CHECK_LENGTH_1_LOGIC2_") > [1] "true" > > debugonce(conformMethod) > > loadNamespace("oligo") > <environment: namespace:oligo> > Warning messages: > 1: multiple methods tables found for ?rowSums? > 2: multiple methods tables found for ?colSums? > 3: multiple methods tables found for ?rowMe...

...until the > > end of August, so people who want to look at it are welcome (it is in R-devel), > > but it is in development and could change pretty much without notice. > > Romain noted that we now support stepping out from one place to another > > function. We also have a debugonce flag that lets you get close to step in, but > > step in is very hard in R. > > > > I am mostly interested in writing tools in R that can be used by anyone that > > wants to write an external debugger and am not that interested in any particular > > external debugger...

..., then the still missing arguments are filled positionally. Unnamed missing arguments are thus left missing. Does that help? Michael On Fri, Nov 30, 2018 at 8:18 AM Emil Bode <emil.bode at dans.knaw.nl> wrote: > > But the main point is where arguments are mixed together: > > > debugonce(plot.default) > > plot(x=1:10, y=, 'l') > ... > Browse[2]> missing(y) > [1] FALSE > Browse[2]> y > [1] "l" > Browse[2]> type > [1] "p" > > I think that's what I fall over mostly: that named, empty arguments behave entirely di...

Thank you. To correct myself, I can indeed reproduce this with R --vanilla too. A reproducible example is: $ R --vanilla R version 3.6.0 Patched (2019-05-31 r76629) -- "Planting of a Tree" ... > Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") > loadNamespace("oligo") Error in omittedSig && (signature[omittedSig] != "missing") :

...frame() with a data argument, should return an informative error message that says that model formulas like this are not supported with new data. As you can see they are supported, but you have to make sure that the objects in the formula can be found in the newdata arg. If this is puzzling, try debugonce(predict.lm) predict(cars.lm, newdata = mtcars[1:5, ) and inspect the newdata object and terms(object). You should see why the terms in the formula are not found in newdata. If you think that something like your idiom for formula is required, maybe you should repost on r-help and say what you ar...

...o have been installed before, too .. which is not quite a "vanilla repr.ex." in my view Worse, I cannot reproduce : > Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") > Sys.getenv("_R_CHECK_LENGTH_1_LOGIC2_") [1] "true" > debugonce(conformMethod) > loadNamespace("oligo") <environment: namespace:oligo> Warning messages: 1: multiple methods tables found for ?rowSums? 2: multiple methods tables found for ?colSums? 3: multiple methods tables found for ?rowMeans? 4: multiple method...

...9;m still running R 3.2.0 (I know, I know...). When trying the following code, I got an error: > library(copula) > fgmCopula(0.8) Error in substr(sc[i], 2, nchar(sc[i]) - 1) : 4 arguments passed to .Internal(nchar) which requires 3 So I do the obvious and try to debug using debug(): > debugonce(fgmCopula) > fgmCopula(0.8) And when I try that, I can step through the complete function without any error. I know that the obvious solution is to update to R 3.2.2, but : - I have absolutely no clue how a function can give an error when used normally, but not return any error when stepping t...

On Thu, Nov 29, 2018 at 1:10 PM S Ellison <S.Ellison at lgcgroup.com> wrote: > > > > > plot(x=1:10, y=) > > > plot(x=1:10, y=, 10:1) > > > > > > In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not > > 'missing' y) > > > In the second case, 10:1 is positionally matched to y despite the

...epr.ex." in my view >>> >>> Worse, I cannot reproduce : >>> >>>> Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") >>>> Sys.getenv("_R_CHECK_LENGTH_1_LOGIC2_") >>> [1] "true" >>>> debugonce(conformMethod) >>>> loadNamespace("oligo") >>> <environment: namespace:oligo> >>> Warning messages: >>> 1: multiple methods tables found for ?rowSums? >>> 2: multiple methods tables found for ?colSums? >>> 3: multipl...

...not quite a "vanilla repr.ex." in my view >> >> Worse, I cannot reproduce : >> >>> Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") >>> Sys.getenv("_R_CHECK_LENGTH_1_LOGIC2_") >> [1] "true" >>> debugonce(conformMethod) >>> loadNamespace("oligo") >> <environment: namespace:oligo> >> Warning messages: >> 1: multiple methods tables found for ?rowSums? >> 2: multiple methods tables found for ?colSums? >> 3: multiple methods tables fo...

...;>>> Worse, I cannot reproduce : >>>> >>>>> Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") >>>>> Sys.getenv("_R_CHECK_LENGTH_1_LOGIC2_") >>>> [1] "true" >>>>> debugonce(conformMethod) >>>>> loadNamespace("oligo") >>>> <environment: namespace:oligo> >>>> Warning messages: >>>> 1: multiple methods tables found for ?rowSums? >>>> 2: multiple methods tables found for ?co...

...e time when mypackage is loaded, and the time when the component of mypackage that calls otherpackage::otherfun is executed) ? MY OWN ATTEMPTS TO UNDERSTAND ============================= What I've done so far I've read the documentation I could find, stepped through loadNamespace using debugonce (several times) with toy packages to gains some insight into what loadNamespace does at the moment (using R3.1.2 on a Windows 64 bit machine), and read the loadNamespace code a few times (though I can't yet claim to follow all of its neat tricks and complexities). My understanding ths far is t...