Hello,
I submitted a package to CRAN that passed all checks in RStudio but failed
when it was tested on Solaris (after it was on CRAN). Now I need to correct
the error and resubmit to CRAN. I would like to avoid using CRAN as a
debugging tool. Is there a way to check packages on Solaris? I am usin
On 09/01/2019 15:03, mike guggis wrote:
Hello,
I submitted a package to CRAN that passed all checks in RStudio but
failed when it was tested on Solaris (after it was on CRAN). Now I need
to correct the error and resubmit to CRAN. I would like to avoid using
CRAN as a debugging tool. Is there
On Wed, 9 Jan 2019 at 15:04, mike guggis wrote:
>
> Hello,
>
> I submitted a package to CRAN that passed all checks in RStudio but failed
> when it was tested on Solaris (after it was on CRAN). Now I need to correct
> the error and resubmit to CRAN. I would like to avoid using CRAN as a
> debug
On 09.01.19 15:03, mike guggis wrote:
> I submitted a package to CRAN that passed all checks in RStudio but
> failed when it was tested on Solaris (after it was on CRAN). Now I need
> to correct the error and resubmit to CRAN. I would like to avoid using
> CRAN as a debugging tool. Is there a way t
Many of the Solaris quirks are documented in R-exts:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Portable-C-and-C_002b_002b-code
In particular:
Mathematical functions such as sqrt are defined in C++ for
floating-point arguments. It is legitimate in C++ to overload these
with ver
For testing, I suggest you use a virtual machine.
You can find the instructions by the link below:
https://github.com/jeroen/solarisvm
Best,
KK
From: Rcpp-devel on behalf of
mike guggis
Date: Wednesday, January 9, 2019 at 6:04 AM
To: "rcpp-devel@lists.r-forge.r-project.org"
Subject: [Rcpp
Thank you Bill,
I have tried gctorture, and low and behold I got an error in some of my code
(Yay!). I was able to pin the gctorture error to something small and
reproducible. It turns out in a one place I created temporary SEXP variables
(see the example below), and I guess these were not pr
In general, once an Rcpp API gives you a SEXP, it is unprotected and
the onus is on your to manage its protection.
In your code:
SEXP intSexp = call1.eval();
Language call2("levels",facSexp);
SEXP levelsSexp = call2.eval();
vals = as< std::vector >(
On 10 January 2019 at 00:23, Fellows, Ian wrote:
| My understanding is that afunc safe to use in a module. Is it also safe to
call from other C++ code, or is lis open to garbage collection?
Every SEXP contains memory owned by R -- we create them that way and when we
return them to R they are in
