RcppCNPy 0.2.3
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
CXX_STD = CXX11
in order to get
C++11 (or the best available subset on older compilers). This brings a
number of changes and opportunities which are frankly too numerous to be
discussed in this short post. But it also permits us, at long last, to use long
long
integer types.
For RcppCNPy, this means that we can finally cover NumPy integer data (along
with the double precision we had from the start) on all
platforms. Python encodes these as an int64, and that type was unavailable
(at least in 32-bit OSs) until we got long long
made available
to us by R.
So today I made the change to depend on R 3.1.0, and select C++11 which
allowed us to free the code from a number if #ifdef
tests. This
all worked out swimmingly and the new package has already been rebuilt for
Windows.
I also updated the vignette, and refreshed its look and feel.
Full changes are listed below.
Changes in version 0.2.3 (2014-04-10)
src/Makevars
now setsCXX_STD = CXX11
which also provides thelong long
type on all platforms, so integer file support is no longer conditional.Consequently, code conditional on
RCPP_HAS_LONG_LONG_TYPES
has been simplified and is no longer conditional.The package now depends on R 3.1.0 or later to allow this.
The vignette has been updated and refreshed to reflect this.
CRANberries also provides a diffstat report for the latest release. As always, feedback is welcome and the rcpp-devel mailing list off the R-Forge page for Rcpp is the best place to start a discussion.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.