Hi,
I am running into a problem when I use the window<- replacement function in R
3.4.0. It will lead to an error when it is called inside a loop, probably
the result of the byte compiler now enabled by default.
When I turn it off, it works again, as in older versions of R. I tested on Win,
Linu
The result of match.call() should be something that would evaluate
correctly in the frame of the fun0() call. While wrapping things in
parentheses is unlikely to cause any problems, arbitrary calls and
symbols would.
Consider the following:
fun0 <- function(a, ...) {
x <- 2L
fun1(...)
}
f
No, I don't think anyone is working on this.
There's a fairly simple workaround for the UTF-16 and UTF-32 iconv
issues: don't attempt to produce character vectors, produce raw vectors
instead. (The "toRaw" argument to iconv() asks for this.) Raw vectors
can contain embedded nulls. Character
I'm noticing some interesting behavior in `match.call` in some corner-ish cases
that arise when you try to use `match.call` to match a "grandparent" function
and there are dots involved:
fun0 <- function(a, ...) fun1(...)
fun1 <- function(b, ...) fun2()
fun2 <- function()
m
"R version 3.4.0 (2017-04-21)" on "x86_64-w64-mingw32" platform
I am using CSVs and other text tables, and text in general (including
regular expressions), on Windows 10.
For me, that means dealing with Windows-1252 and UTF-8 encoding, with UTF-16
and UTF-32 as helpful curiosities.
Something as
Hi,
please find attached a tiny patch
that improves the reproducibility of R
as built in openSUSE
There are other sources of non-reproducibility as can be seen in
the diffs on
http://rb.zq1.de/compare.factory-20170428/R-base-compare.out
e.g. there are timestamps in /usr/lib64/R/library/boot/Meta
