I've made a small enhancement to R that would help developers better control
what versions of code we're using where. Basically, to load a package in R,
one currently does:
library(whateverPackage)
and with the enhancement, you can ensure that you're getting at least version X
Context: R2.15-0 on Ubuntu.
1. I get a WARNING from CMD check for Package vignette(s) without
corresponding PDF:
In this case the vignettes directory had both the pdf and Rnw; do I
need to move the pdf to inst/doc?
I'm reluctant to add the pdf to the svn source on Rforge, per the
usual
In DESCRIPTION if I set LazyLoad to 'yes' will data.table (for example)
then be byte compiled for users who install the binary package from CRAN
on Windows?
This question is based on reading section 1.2 of this document :
http://www.divms.uiowa.edu/~luke/R/compiler/compiler.pdf
I've searched
For 1, you should run R CMD check on the tar ball (pkg_x.x.tar.gz)
from R CMD build instead of the source directory. R CMD build will
build the PDF vignette into the tar ball.
For 2, I have been confused by ./vignettes vs ./inst/doc since
./vignettes was introduced. I might be able to figure it
I recently started using R 2.14.0 on a new machine and i am experiencing
what seems like unusually greedy memory use. It happens all the time, but
to give a specific example, let's say i run the following code
for(j in 1:length(files)){
load(file.path(dump.dir, files[j]))
On Apr 12, 2012, at 00:53 , andre zege wrote:
I recently started using R 2.14.0 on a new machine and i am experiencing
what seems like unusually greedy memory use. It happens all the time, but
to give a specific example, let's say i run the following code
for(j in
On 12-04-11 04:41 PM, Terry Therneau wrote:
Context: R2.15-0 on Ubuntu.
1. I get a WARNING from CMD check for Package vignette(s) without
corresponding PDF:
In this case the vignettes directory had both the pdf and Rnw; do I need
to move the pdf to inst/doc?
Yes, you need to put the pdf in
You are quite right that my exec time would seriously go down if i
pre-allocate and not even use abind, just assign into the preallocated
matrix. The reason i didn't do it here is that this is a part of some
utility function that doesn't know the sizes of chunks that are on disk
untill it reads
Leaving aside what's going on inside abind::abind(), maybe the
following sheds some light on what's is being wasted:
# Preallocate (probably doesn't make a difference because it's a list)
mat.data - vector(list, length=length(files));
for (j in 1:length(files)){
vars -
On 11/04/2012 20:36, Matthew Dowle wrote:
In DESCRIPTION if I set LazyLoad to 'yes' will data.table (for example)
then be byte compiled for users who install the binary package from CRAN
on Windows?
No. LazyLoad is distinct from byte compilation. All installed packages
use lazy loading
10 matches
Mail list logo
