5
5
Version 0.11.0 of the Rcpp package is now on CRAN and its mirrors.
6
6
7
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 of the changes implemented between the last announcement for version
10
- 0.10.0 and this new can be found in the NEWS and ChangeLog files which are
11
- included in the package.
8
+ build system, as well as improvements to existing features and bugfixes.
9
+
10
+ Complete details of the changes implemented between the last announcement for
11
+ version 0.10.0 and this new can be found in the NEWS and ChangeLog files
12
+ which are included in the package.
12
13
13
14
14
15
@@ -22,8 +23,7 @@ Issue 08) paper (also included in the package as the "Rcpp-introduction" pdf
22
23
vignette) and a book "Seamless R and C++ Integration with Rcpp" (2013,
23
24
Springer, useR! Series).
24
25
25
- As of early 2014, Rcpp is used by over 160 other CRAN packages making it the
26
- most widely-used language interface for R.
26
+ As of early 2014, Rcpp is used by over 160 other CRAN packages.
27
27
28
28
Several key features of the new 0.11.0 release are described below.
29
29
@@ -38,16 +38,17 @@ using Rcpp need to be reinstalled.
38
38
We provide a simple helper script at
39
39
https://github.com/RcppCore/rcpp-logs/blob/master/scripts/showReverseRcppDepends.r
40
40
to identidy which of your currently-installed packages use Rcpp, and need to
41
- be rebuilt.
41
+ be rebuilt / reinstalled .
42
42
43
43
44
44
45
45
===== Simpler Building with Rcpp =====
46
46
47
47
Thanks to the 'LinkingTo:' directive, R already instructed the compiler where
48
48
to fine header files when writing code with Rcpp. The package now uses the
49
- registration facilities in R (see Section 5.4 in Writing R Extensions). With
50
- just an 'Imports: Rcpp' in DESCRIPTION along with an explicit import
49
+ registration facilities in R (see Section 5.4 in Writing R Extensions).
50
+
51
+ With just an 'Imports: Rcpp' in DESCRIPTION along with an explicit import
51
52
statement in the NAMESPACE file such 'importFrom(Rcpp, evalCpp)' all required
52
53
Rcpp code will be properly instantiated without any explicit linking. [ Note
53
54
that just using 'import(Rcpp)' is not sufficient, but any exported C++
@@ -89,7 +90,7 @@ and Rcpp attributes takes care of the rest.
89
90
90
91
===== Memory management =====
91
92
92
- A number of internal data structures were rewritten.
93
+ A number of internal data structures have been rewritten.
93
94
94
95
95
96
@@ -129,7 +130,7 @@ used resource under the [rcpp] tag:
129
130
On behalf of the Rcpp Core team,
130
131
131
132
Dirk Eddelbuettel
132
- January 2014
133
+ February 2014
133
134
134
135
135
136
0 commit comments