similar to: R CMD check warning about compiler warning flags

>> 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: >> https://github.com/wch/r-source/commit/2e80059 > > That is not the canonical R sources. Yes, that is obvious. The main page for that repository says it is

>>>>> Duncan Murdoch <murdoch.duncan at gmail.com> >>>>> on Thu, 21 Dec 2017 14:23:13 -0500 writes: > On 21/12/2017 1:02 PM, 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

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

On 22/12/2017 10:46 AM, Marc Schwartz wrote: > Hi, > > See inline below. > > >> On Dec 22, 2017, at 9:12 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >> >>>>>>> Duncan Murdoch <murdoch.duncan at gmail.com> >>>>>>> on Thu, 21 Dec 2017 14:23:13 -0500 writes: >> >>> On 21/12/2017 1:02

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: > https://github.com/wch/r-source/commit/2e80059 That is not the canonical R sources. And your description seems wrong: there is now

On 21/12/2017 1:02 PM, 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: >>> https://github.com/wch/r-source/commit/2e80059 >> >> That is not the canonical R

Hi, See inline below. > On Dec 22, 2017, at 9:12 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > >>>>>> Duncan Murdoch <murdoch.duncan at gmail.com> >>>>>> on Thu, 21 Dec 2017 14:23:13 -0500 writes: > >> On 21/12/2017 1:02 PM, Winston Chang wrote: >>>>> On recent builds of R-devel, R CMD check gives

On 25/12/2017 7:00 AM, I?aki ?car wrote: > 2017-12-25 12:30 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: >> The one negative aspect of Winston's effort is caused by this weakness. If >> you tell me that something happened in revision 73909, I know it was recent. >> If you tell me that something appeared in commit 2e80059, it wastes my time >> looking

On 20/12/2017 5:48 PM, Hadley Wickham wrote: > 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.

I'm getting an R CMD check warning with a package (call it package A) that defines an S3 method but not the generic. The generic is defined in another package (package B). Package A imports the S3 generic from B. And there's one additional detail: the generic overrides a function in the stats package. I've created a minimal test package which reproduces the problem:

) On Wed, Apr 5, 2017 at 2:59 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > > >>>>> Winston Chang <winstonchang1 at gmail.com> > >>>>> on Tue, 4 Apr 2017 15:29:40 -0500 writes: > > > I've done some more investigation into the problem, and it is very > > difficult to pin down. What it looks like is

I've been seeing warnings when unloading packages. They can be seen with the shiny and sp packages, among others (this is on R 3.0.2). For example: > library(sp) > unloadNamespace('sp') Warning messages: 1: In FUN(X[[2L]], ...) : Created a package name, ‘2013-12-19 12:14:24’, when none found 2: In FUN(X[[2L]], ...) : Created a package name, ‘2013-12-19 12:14:24’, when none

> > >> I've done some more investigation into the problem, and it is very difficult to pin down. What it looks like is happening is roughly like this: - `p` is an environment and `p$e` is also an environment. - There is a loop. In each iteration, it looks for one item in `p$e`, saves it in a variable `x`, then removes that item from `p$e`. Then it invokes `x()`. The loop runs

When running R CMD check on a package, we are encountering an error on R-devel (as of 72457) on Linux. Unfortunately, it is very hard to reproduce, and almost any change to the code makes the error go away. I believe that this is due to a bug in R-devel, which has been present since at least commit 72128 (on 2017-02-06). The test error occurs when R CMD check is run on Travis CI (on Ubuntu

In R 3.2.4, if you ran download.file(method="libcurl"), it issues a HTTP GET request for the file. However, in R 3.3.0, it issues a HTTP HEAD request first, and then a GET requet. This can result in problems when the web server gives an error for a HEAD request, even if the file is available with a GET request. Is it possible to tell download.file to simply send a GET request, without

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its

On Windows, grep(fixed=TRUE) throws errors with some UTF-8 strings. Here's an example (must be run on Windows to reproduce the error): Sys.setlocale("LC_CTYPE", "chinese") y <- rawToChar(as.raw(c(0xe6, 0xb8, 0x97))) Encoding(y) <- "UTF-8" y # [1] "?" grep("\n", y, fixed = TRUE) # Error in grep("\n", y, fixed = TRUE) : invalid

Hi everyone: I?m one of the interns at RStudio this summer working on a project that helps teachers grade student code. I found an unexpected behaviour with the |==| operator when comparing |quote|d expressions. Example 1: |u <- quote(tidyr::gather(key = key, value = value, new_sp_m014:newrel_f65, na.rm = TRUE)) s <- quote(tidyr::gather(key = key, value = value,

Could of requests: 1) Is there any example or writeup on the difficulties of extending reference classes across packages? Just so I can fully understand the issues. 2) In what sorts of situations does the performance of reference classes cause problems? Sure, it's an order of magnitude slower than constructing a simple environment, but those timings are in microseconds, so one would need a

When a reference class method is accessed with .self$x, it has different behavior from .self[['x']]. The former copies the function to the object's environment (with some attributes attached), and the latter just return NULL (unless it has already been accessed once with .self$x). Is this how it's supposed to work? Here's an example that illustrates: