On 18 November 2012 at 15:25, Thell Fowler wrote:
| Is there some kind of a stance against 'auto'?
For the CRAN gatekeepers, '-std=c++0x' and '-std=c++11' are considered
non-portable. We simply have to wait til this becomes a) the g++ default
and b) that that g++ version because the default inst
On 18 November 2012 at 21:17, Romain Francois wrote:
| You don't need to wrap an "Rcpp::S4", as these are already R objects, so
| an implicit conversion to SEXP already exists.
|
| Same here:
|
| vS4.slot("exp") = wrap( exp );
|
| you don't need this wrap, you should be able to just use:
|
|
On Sun, Nov 18, 2012 at 2:17 PM, Romain Francois
wrote:
> Hello,
>
> You don't need to wrap an "Rcpp::S4", as these are already R objects, so
> an implicit conversion to SEXP already exists.
>
> Same here:
>
>
> vS4.slot("exp") = wrap( exp );
>
> you don't need this wrap, you should be able to jus
Hello,
You don't need to wrap an "Rcpp::S4", as these are already R objects, so
an implicit conversion to SEXP already exists.
Same here:
vS4.slot("exp") = wrap( exp );
you don't need this wrap, you should be able to just use:
vS4.slot("exp") = exp ;
for the same reason, exp is already an
Hi Thell,
On 18 November 2012 at 13:03, Thell Fowler wrote:
| Hi all.
|
| I've been doing some testing on how to get arbitrary precision numbers out of
| c++ and into R. The following example inline Rcpp code generates an RcppMpfr
| cxxfunction plugin for wrapping to the Rmpfr S4 "mpfr1" objec
Forgot to mention I don't have access to 64bit at the moment, so that
hasn't been tested at all, and just the 32bit stuff has been played with.
___
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/
Hi all.
I've been doing some testing on how to get arbitrary precision numbers out
of c++ and into R. The following example inline Rcpp code generates an
RcppMpfr cxxfunction plugin for wrapping to the Rmpfr S4 "mpfr1"
object. There are local include paths that need adjusting (for now) to
your
