On 13-12-02 5:25 PM, Peder Axensten wrote:
Duncan,
As soon as I read your letter I realized the logic. I followed your advice and
the warnings are gone. I don’t know how long it would have taken me to see it
myself, but probably quite some time – thank you!
I do think it’s a pity, in this spe
Duncan,
As soon as I read your letter I realized the logic. I followed your advice and
the warnings are gone. I don’t know how long it would have taken me to see it
myself, but probably quite some time – thank you!
I do think it’s a pity, in this special case, that I can’t put the returning
fu
On 02/12/2013 1:39 PM, Swapnil Gaikwad wrote:
Hi Team,
I downloaded the R 3.0.2 and, built and installed it
using Intel compilers (icc and ifort) from Intel parallel studio 2013,
sp1. After performing make tried to check it using 'make check'. Most of
the tests passed successfull
Hi Team,
I downloaded the R 3.0.2 and, built and installed it
using Intel compilers (icc and ifort) from Intel parallel studio 2013,
sp1. After performing make tried to check it using 'make check'. Most of
the tests passed successfully but while checking a 'stats' package I saw
On 02/12/2013 9:57 AM, Peder Axensten wrote:
I’m in the process of preparing a package for CRAN.
The package is called “exportR” and since it really just consists of one
function, I found it natural to call it “exportR” too.
The function returns a function that does the actual job, but it is s
I’m in the process of preparing a package for CRAN.
The package is called “exportR” and since it really just consists of one
function, I found it natural to call it “exportR” too.
The function returns a function that does the actual job, but it is set up to
work in different ways, depending on
Following up on the thread spawned a while back, I just wanted to say that I
appreciate today's RSS serving of R-devel NEWS:
CHANGES IN R-devel PACKAGE INSTALLATION
There is _experimental_ support for compiling C++11 code in packages. The
file ‘src/Makevars’ or ‘src/Makevars.win’ should
Hi,
Just to add some information and to clarify why I feel this is an
important issue.
If you have a S4 method with a default argument, it seems that you can
not catch the warnings
emitted during their evaluation. It matters because on some occasions
those warnings carry an essential information,
