On Mon, Mar 3, 2014 at 2:50 PM, Simon Urbanek
wrote:
> Jens,
>
> On Mar 3, 2014, at 3:35 PM, Jens Oehlschlägel <
> jens.oehlschlae...@truecluster.com> wrote:
>
> >
> > Well, I did read, for example "Writing R Extensions" (Version 3.1.0
> Under development (2014-02-28)) chapter "5.9.10 Named object
I think the server that runs the valgrind checks is still running the
old version of your package (2.17) not the new one (2.18). Wait for an
update.
Martyn
On Mon, 2014-03-17 at 17:26 +, Jarrod Hadfield wrote:
> Hi,
>
> I am sorry if this is perceived as a C++ question rather than an R
> q
Hi Martyn,
Thanks for the email - you are right. I thought I was getting the
valgrind checks on my submission, not the version on CRAN.
Kind Regards,
Jarrod
Quoting Martyn Plummer on Tue, 18 Mar 2014 16:53:55 +:
I think the server that runs the valgrind checks is still running the
This came up again recently with an irreproducible paper. Below an
attempt to make a case for extending the r-devel/r-release cycle to
CRAN packages. These suggestions are not in any way intended as
criticism on anyone or the status quo.
The proposal described in [1] is to freeze a snapshot of CRA
Hello R-core developers,
The upcoming release of R-3.1.0 is exciting, especially the support
structure changes for c++11!
But, just the other day I encountered an issue with the package
creation tools within Rcpp and Dirk referred me to 'Writing R
Extensions' [footnote 13] along with the comment
