similar to: Warning: use of NULL environment is deprecated (in R CMD check)

Help for help says: The 'topic' argument may also be a function call, to ask for documentation on a corresponding method. See the section on method documentation. and The authors of formal ('S4') methods can provide documentation on specific methods, as well as overall documentation on the methods of a particular function. The

On Wed, Dec 20, 2017 at 4:26 PM, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote: > On 20/12/2017 17:42, Winston Chang wrote: >> >> On recent builds of R-devel, R CMD check gives a WARNING when some >> compiler warning flags are detected, such as -Werror, because they are >> non-portable. This appears to have been added in this commit: >>

Hi all (but especially Kurt), Would it be possible to have a flag to R CMD check that warned on partial all matches, i.e. turning on: options( warnPartialMatchDollar = TRUE, warnPartialMatchArgs = TRUE, warnPartialMatchAttr = TRUE ) I think this is good practice for package code. I don't think it can currently be made part of the default (because sometimes the warnings come from

I'm always forgetting to update the date in DESCRIPTION. Would it be possible to add a warning to R CMD check if it's old? Hadley -- http://had.co.nz/

I was a bit suprised to note that demo files are not run as part of R CMD check. This seems out of keeping with the philosophy of running all code contained in the package (in the source, in examples etc). Should demo files be checked as part of R CMD check? Hadley

Jan and Hadley, There's also the issue of tests, vignettes, or examples requiring Suggested packages (one of the core applications of Suggests, in fact). These are all checked by R CMD check, so to ensure any package which should pass check would do so without suggested packages installed would require turning all of those checks off, which takes quite a few of the teeth out of R CMD check

Hi all, Does anyone have any suggestions for debugging the execution of examples by R CMD check? The examples work fine when I run them from a live R prompt, but I get errors when they are run by R CMD check. Thanks, Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/

Make the example print out Sys.getenv() and then manually inspect? Otherwise, you'll need to debug the code by adding print statements. Something clearly is not as you expect, so you need carefully empirically verify your assumptions about the inputs to and environment of the function. Hadley On Fri, May 15, 2015 at 7:05 AM, Charles Determan <cdetermanjr at gmail.com> wrote: > Does

On Tue, Oct 13, 2015 at 4:43 PM, Hadley Wickham <h.wickham at gmail.com> wrote: > Seems easy enough to write yourself: > > where <- function(x, env = parent.frame()) { > if (identical(env, emptyenv())) > return(NULL) > if (exists(x, envir = env, inherits = FALSE)) > return(env) > where(x, parent.env(env)) > } > > sample2 <-

Please read this first: http://www.perceptualedge.com/articles/visual_business_intelligence/dual-scaled_axes.pdf It's a reasoned discussion of why it's a bad idea and proposes some alternative methods. Another good article is: K. W. Haemer. Double scales are dangerous. The American Statistician, 2(3):24?24, 1948. People have been advising dual-axis plots for (at least) 60 years! Hadley

Hi all, Would you generally consider NULL to be a vector? Base R functions are a little inconsistent: ## In favour ``` r identical(as.vector(NULL), NULL) #> [1] TRUE identical(as(NULL, "vector"), NULL) #> [1] TRUE # supports key vector vector generics length(NULL) #> [1] 0 NULL[c(3, 4, 5)] #> NULL NULL[[1]] #> NULL ``` ## Against ``` r is.vector(NULL) #> [1]

Hi all, Am I using the correct syntax to set a custom R_LIBS when running R CMD INSTALL from the command line? I get: R_LIBS=/Users/hadley/R-dev R CMD INSTALL aL3xa-rapport-08e68ca/ # Desktop : R_LIBS=/Users/hadley/R-dev R CMD INSTALL aL3xa-rapport-08e68ca/ # * installing to library ?/Users/hadley/R? # ERROR: dependency ?ascii? is not available for package ?rapport? But: ls

On Fri, Mar 3, 2017 at 9:55 AM, Hadley Wickham <h.wickham at gmail.com> wrote: >> But, how you propose a warning-to-error transition should be made >> without wreaking havoc? Just flip the switch in R-devel and see CRAN >> and Bioconductor packages break overnight? Particularly Bioconductor >> devel might become non-functional (since at times it requires >>

Hi all, It's possible to capture the expression associated with a promise (using substitute). Is there any way to capture the environment associated with a promise? Similarly, is there any way to tell if something is a promise without accidentally evaluating it? Thanks! Hadley -- RStudio / Rice University http://had.co.nz/

On 03/01/2018 6:11 PM, Uwe Ligges wrote: > > > On 26.12.2017 00:45, Juan Telleria wrote: >> However, and hope not to be off-topic, a git repository (github, gitlab, >> codeplex, etc., not just solely github) could constitute a tidy approach, >> and make things easier to R Core :) >> >> By putting the focus on version control, the line of changes made with

It would be nice if R CMD check ran any file in the tests directory that has "one of the extensions .R, .S, .q, .r, or .s" - i.e. it should match the files processed in the R directory. Hadley -- http://had.co.nz/

How can I suppress this warning? > options(warn = -10) > list(1,2,3,) Warning: a final empty element has been omitted the part of the args list of 'list' being evaluated was: (1, 2, 3, ) [[1]] [1] 1 [[2]] [1] 2 [[3]] [1] 3 > suppressWarnings(list(1,)) Warning: a final empty element has been omitted the part of the args list of 'list' being evaluated was: (1, )

$ R CMD install ggplot2 ... scale-usage-d1 text html latex scale_brewer text html latex example perl(90227) malloc: *** mmap(size=314880000) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug Out of memory! ERROR: building help failed for package 'ggplot2' Any ideas?

Hi all, Is it possible to determine the environment in which a promise will be evaluated? e.g. f <- function(code) { force(code) } f({ a <- 1 b <- 2 }) Is there any way to tell from within f that a and b will be created in the global environment? Thanks, Hadley -- http://had.co.nz/

Dear R team, Are suggested dependencies mandatory in context of `R CMD check` when using env var `_R_CHECK_FORCE_SUGGESTS_=FALSE`? Suggested dependencies are nice because are optional. But that feature often isn't valid when trying to run `R CMD check` on them. I would like to use `export _R_CHECK_FORCE_SUGGESTS_=FALSE`, which according to the comment in `tools/R/check.R`: > The