|
4 | 4 |
|
5 | 5 | \section{Changes in Rcpp version 0.10.5 (future)}{ |
6 | 6 | \itemize{ |
7 | | - |
8 | 7 | \item Changes in Rcpp API: |
9 | 8 | \itemize{ |
10 | 9 | \item Add \code{#defined(__sun)} to lists of operating systems to |
|
24 | 23 | \code{String} and \code{VALUE} is either a primitive type (int, double) |
25 | 24 | or a type that wraps. Examples : |
26 | 25 | \itemize{ |
27 | | - \item \code{std::map<int, double>} : we can make a String from an int, |
28 | | - and double is primitive |
29 | | - \item \code{boost::unordered_map<double, std::vector<double> >}: we can make |
30 | | - a String from a double and \code{std::vector<double>} can wrap itself |
| 26 | + \item \code{std::map<int, double>} : we can make a String from an int, |
| 27 | + and double is primitive |
| 28 | + \item \code{boost::unordered_map<double, std::vector<double> >}: we can make |
| 29 | + a String from a double and \code{std::vector<double>} can wrap itself |
31 | 30 | } |
32 | 31 | Other examples of this are included at the end of the \code{wrap} unit test |
33 | 32 | file (\code{runit.wrap.R} and \code{wrap.cpp}). |
|
36 | 35 | \code{vector<Foo>}, ... An example is included in the \code{wrap} unit test |
37 | 36 | file |
38 | 37 | } |
39 | | - |
40 | 38 | \item Changes in Attributes: |
41 | 39 | \itemize{ |
42 | | - \item Objects exported by a module (i.e. by a \code{RCPP_MODULE} call |
43 | | - in a file that is processed by \code{sourceCpp}) are now directly |
44 | | - available in the environment. We used to make the module object |
45 | | - available, which was less useful. |
46 | | - \item A plugin for 'openmp' has been added to support use of OpenMP. |
47 | | - \item \code{Rcpp::export} now takes advantage of the more flexible |
48 | | - \code{as<>}, handling constness and referenceness of the input types. |
49 | | - For users, it means that for the parameters of function exported by modules, |
50 | | - we can now use references, pointers and const versions of them. |
51 | | - The Module.cpp file has an example. |
| 40 | + \item Objects exported by a module (i.e. by a \code{RCPP_MODULE} call |
| 41 | + in a file that is processed by \code{sourceCpp}) are now directly |
| 42 | + available in the environment. We used to make the module object |
| 43 | + available, which was less useful. |
| 44 | + \item A plugin for \code{openmp} has been added to support use of OpenMP. |
| 45 | + \item \code{Rcpp::export} now takes advantage of the more flexible |
| 46 | + \code{as<>}, handling constness and referenceness of the input types. |
| 47 | + For users, it means that for the parameters of function exported by modules, |
| 48 | + we can now use references, pointers and const versions of them. |
| 49 | + The file \code{Module.cpp} file has an example. |
52 | 50 | } |
53 | | - |
54 | 51 | \item Changes in Modules: |
55 | 52 | \itemize{ |
56 | 53 | \item We can now expose functions and methods that take |
57 | 54 | \code{T&} or \code{const T&} as arguments. In these situations |
58 | 55 | objects are no longer copied as they used to be. |
59 | 56 | } |
60 | | - |
61 | 57 | \item Changes in sugar: |
62 | 58 | \itemize{ |
63 | | - \item \code{is_na} supports classes \code{DatetimeVector} and |
64 | | - \code{DateVector} |
| 59 | + \item \code{is_na} supports classes \code{DatetimeVector} and |
| 60 | + \code{DateVector} |
| 61 | + } |
| 62 | + \item Changes in Rcpp documentation: |
| 63 | + \itemize{ |
| 64 | + \item The vignettes have been moved from \code{inst/doc/} to the |
| 65 | + \code{vignettes} directory which is now preferred |
| 66 | + \item The unitTest vignette has been disabled as no longer builds |
| 67 | + when called from \code{R CMD check}; |
65 | 68 | } |
66 | | - |
67 | 69 | \item Deprecation of \code{RCPP_FUNCTION_*}: |
68 | 70 | \itemize{ |
69 | 71 | \item The macros from the \code{preprocessor_generated.h} file |
|
0 commit comments