With this set-up
options(warn = 1)
tf <- tempfile()
finalizer <- function(obj) {
message("finalizer")
close(obj$f)
}
this code works
ev <- new.env()
ev$f <- file(tf, "w")
reg.finalizer(ev, finalizer)
rm(ev)
gc()
whereas this (reversing the order of file() and reg.finalizer())
ev <- ne
Hi,
In both R 2.13 and the SVN trunk, I observe odd behaviour with the
--max-vsize command-line argument:
1. passing a largeish value (about 260M or greater) makes mem.limits()
report NA for the vsize limit; gc() continues to report a value...
2. ...but that value (and the actual limit) is wr
In principle, two separately developed packages could use the same class
name, and a user could then attach both and attempt to use methods for
both classes.
That has never worked, but some changes have been added to r-devel to
handle this case. The changes involve extending the "signature" c
Most if not all packages will need a re-installation, not only those you
talked about (in particular there is a new snow on CRAN already). Hence
I think it is not worth the effort to find out what "old" means. Please
note this may change during the development cycle and you may even need
one or
> Jonathan Dushoff
> on Thu, 30 Jun 2011 14:09:30 -0400 writes:
> Under Details, the documentation says "[if Rowv or Colv] is 'NULL',
> _no reordering_ will be done for the corresponding side." In fact, as
> explained elsewhere in the documentation, 'NA' is required, not
> "iw" == ivo welch
> on Fri, 8 Jul 2011 20:47:08 -0700 writes:
iw> in the documentation for "by", please change the "See
iw> also" section to \seealso{\code{\link{tapply}},
iw> \code{\link{simplify2array}}, \code{\link{ave}}}
iw> (simplify2array, by, and ave should p
On Wed, 20 Jul 2011, Prof Brian Ripley wrote:
1) The current R-patched should compile src/extra/xdr on 32-bit Linux
systems.
2) Longer-term or on a 64-bit platform the solution is to make use of
libtirpc: you would need both this installed (common now) and its headers
(unlikely).
Then if y
On Wed, 20 Jul 2011, David A. Johnston wrote:
I understand that the coercion to a list is somewhat trivial. The coercion
is a little less obvious when apply()'s output is a matrix. For example,
x = matrix(1:12, 3, 4)
apply(x, 1, range)
[,1] [,2] [,3]
[1,]123
[2,] 10 11
Dear list,
I am using the foreach/doSNOW packages. I want to compute some data parallel
and save results in every iteration into a text or CSV file, but then I see
in file there are some errors (some data is not saved to file and there are
empty lines). I have tested every function to append dat
I understand that the coercion to a list is somewhat trivial. The coercion
is a little less obvious when apply()'s output is a matrix. For example,
> x = matrix(1:12, 3, 4)
> apply(x, 1, range)
[,1] [,2] [,3]
[1,]123
[2,] 10 11 12
> structure(as.list(as.data.frame(apply(
10 matches
Mail list logo
