Hello,
(may contains traces of personal opinions)
My motivation for starting Rcpp11 were:
- Assuming C++11, which is nicer to use and teach. Rcpp still wants to be
compatible with older standard, which essentially means that even if I write
something new using C++11, I still have to figure ou
Le 17 avr. 2014 à 09:42, Hao Ye a écrit :
> Hi Romain,
>
> Thanks for the explanation -- I was curious about the difference between Rcpp
> and Rcpp11, as well.
>
> What might help you deciding is that in Rcpp11, we did not retain some
> features such as modules and date/time related classes
On 17 April 2014 at 09:24, Romain François wrote:
| Now, as Dirk says, you can use C++11 with Rcpp. Just as much as you can use
C++11 with vanilla .Call/.C.
Yes of course.
As R in a C program, and as .C (no SEXP) and .Call (SEXP interface) are C
interfaces, Rcpp and Rcpp11 are in the exact sa
Earlier this week we passes a new milestone: there are now 200 packages on
CRAN which use Rcpp. And with the BioConductor 2.14 release, there are now
another 27 packages in BioConductor.
This is a very humbling number, and we are very happy that Rcpp is finding
such wide, and rapidly growing, us
Hi, all
I am new to Rcpp and might need some of your help, thanks a lot.
I was trying to compile my Rcpp program in eclipse. But I met a lot of
errors when I was trying to do so. Most of the error comes from the
String.h. Here is the command and part of error:
*g++ -DINSIDE -ID:/R/R-3.1.0/include
Wen,
On 18 April 2014 at 09:22, Wen YOU wrote:
| I am new to Rcpp and might need some of your help, thanks a lot.
| I was trying to compile my Rcpp program in eclipse. But I met a lot of errors
| when I was trying to do so. Most of the error comes from the String.h. Here is
| the command and part
