[R] R Interface to C / C++
mailinglist.honeypot at gmail.com
Wed Nov 30 01:14:40 CET 2011
IMHO, if you will be focussing mostly in incorporating C/C++ in your
own packages you build, instead of wanting to go into other mixed R/C
packages to change them up, I'd go with C++ together with the Rcpp
Rcpp makes lots of things easier on your end, that having been said,
you should still understand how the mechanics of the .Call interface
works and what SEXPs are, and how you manipulate them w/o using Rcpp.
On Tue, Nov 29, 2011 at 7:04 PM, Axel Urbiz <axel.urbiz at gmail.com> wrote:
> Dear List,
> I’d like to modify the R rpart package source code to add a new split
> criterion. I’m familiar with R, but not at all with C or C++.
> I understand C and C++ are quite different, and I don’t have the time to
> learn both, so my questions are (i) which one should I learn for the
> specific task mentioned above? (I understand rpart routines are written in
> C, but want to check this), (ii) more generally, which one would you
> recommend me to learn for the purpose of writing interfaces from R to any
> of these languages? Besides the specific task mentioned above, I’d like to
> invest my time in learning something that I can use for any later R package
> building projects.
> Thanks for any advice.
> [[alternative HTML version deleted]]
> R-help at r-project.org mailing list
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
Graduate Student: Computational Systems Biology
| Memorial Sloan-Kettering Cancer Center
| Weill Medical College of Cornell University
Contact Info: http://cbio.mskcc.org/~lianos/contact
More information about the R-help