|
| 1 | + |
| 2 | + |
| 3 | +===== Summary ===== |
| 4 | + |
| 5 | +Version 0.11.0 of the Rcpp package is now on CRAN and its mirrors. |
| 6 | + |
| 7 | +This new release brings a number of new features, most noticably a simplified |
| 8 | +build, as well as improvements to existing features and bugfixes. Complete |
| 9 | +details can be found in the NEWS and ChangeLog files which are included in |
| 10 | +the package. |
| 11 | + |
| 12 | + |
| 13 | + |
| 14 | +===== Overview ===== |
| 15 | + |
| 16 | +Rcpp is an R package and associated C++ library for seamless integration |
| 17 | +between C++ and R. |
| 18 | + |
| 19 | +It has been described in a Journal of Statistical Software (2011, Vol 40, |
| 20 | +Issue 08) paper (also included in the package as the "Rcpp-introduction" pdf |
| 21 | +vignette) and a book "Seamless R and C++ Integration with Rcpp" (2013, |
| 22 | +Springer, useR! Series). |
| 23 | + |
| 24 | +As of early 2014, Rcpp is used by over 160 other CRAN packages making it the |
| 25 | +most widely-used language interface for R. |
| 26 | + |
| 27 | +Several key features of the new 0.11.0 release are described below. |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +===== Building with Rcpp ===== |
| 32 | + |
| 33 | +Thanks to the 'LinkingTo:' directive, R already instructed the compiler where |
| 34 | +to fine header files when writing code with Rcpp. The package now uses the |
| 35 | +registration facilities in R (see Section 5.4 in Writing R Extensions). With |
| 36 | +just an 'Imports: Rcpp' in DESCRIPTION along with an explicit import |
| 37 | +statement in the NAMESPACE file such 'importFrom(Rcpp, evalCpp)' all required |
| 38 | +Rcpp code will be properly instantiated without any explicit linking. [ Note |
| 39 | +that just using 'import(Rcpp)' is not sufficient, but any exported C++ |
| 40 | +identifier should do -- evalCpp is nice and short. ] |
| 41 | + |
| 42 | +The key benefit is that package should no longer require files src/Makevars |
| 43 | +and src/Makevars.win to link with Rcpp, and many packages will be able to |
| 44 | +retire these values. The exception, of course, is the case where the package |
| 45 | +links against an external library. |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +===== Rcpp attributes ===== |
| 50 | + |
| 51 | +Rcpp attributes were a key innovation in the 0.10.0; they have matured |
| 52 | +further and have now become the standard way to build code with Rcpp. See |
| 53 | +the dedicated vignette for details. |
| 54 | + |
| 55 | + |
| 56 | +==== C++11 Support ===== |
| 57 | + |
| 58 | +R 3.1.0, to be released in a few month, will permit compilation using C++11, |
| 59 | +the newest C++ standard -- including for packages going to CRAN. Rcpp had |
| 60 | +already supported 'local' builds using C++11 since version 0.10.3, simply add |
| 61 | + |
| 62 | + [[Rcpp::plugins(cpp11)]] |
| 63 | + |
| 64 | +and Rcpp attributes takes care of the rest. |
| 65 | + |
| 66 | + |
| 67 | +===== Memory management ===== |
| 68 | + |
| 69 | +A number of internal data structures were rewritten. |
| 70 | + |
| 71 | + |
| 72 | + |
| 73 | +===== Links ===== |
| 74 | + |
| 75 | +Rcpp site: |
| 76 | + http://www.rcpp.org |
| 77 | + |
| 78 | +Dirk's Rcpp page: |
| 79 | + http://dirk.eddelbuettel.com/code/rcpp.html |
| 80 | + |
| 81 | +GitHub page: |
| 82 | + https://github.com/RcppCore/Rcpp |
| 83 | + |
| 84 | +R-forge project page: |
| 85 | + http://r-forge.r-project.org/projects/rcpp/ |
| 86 | + |
| 87 | +Google+: |
| 88 | + https://plus.google.com/b/107029540907667241299/107029540907667241299/posts |
| 89 | + |
| 90 | + |
| 91 | + |
| 92 | +===== Support ===== |
| 93 | + |
| 94 | +Questions about Rcpp should be directed to the Rcpp-devel mailing list |
| 95 | + https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel |
| 96 | + |
| 97 | +While we prefer the mailing list, StackOverflow has also become a frequently |
| 98 | +used resource under the [rcpp] tag: |
| 99 | + http://stackoverflow.com/questions/tagged/rcpp |
| 100 | + |
| 101 | + |
| 102 | + |
| 103 | +On behalf of the Rcpp Core team, |
| 104 | + |
| 105 | + Dirk Eddelbuettel |
| 106 | + January 2014 |
| 107 | + |
| 108 | + |
| 109 | + |
0 commit comments