Re: [Rcpp-devel] "binding" Rcpp::InternalFunction or Rcpp::CppFunction

2014-08-04 Thread Christian Authmann
On 01.08.2014 13:45, Dirk Eddelbuettel wrote: But beyond those drawbacks you can use C++11 (and even C++14 if your compiler supports it) in your Rcpp packages on CRAN now. See RcppBDT and RcppCNPy for the mechanics. Great. Just creating a CppFunction that wraps std::function simplified the c

Re: [Rcpp-devel] "binding" Rcpp::InternalFunction or Rcpp::CppFunction

2014-08-01 Thread Dirk Eddelbuettel
Christian, I don't have time comment in full but two brief comments: On 1 August 2014 at 13:17, Christian Authmann wrote: | And we cannot use c++11's std::function in rcpp since CRAN won't allow it | (or did that change?) We can use C++11 (since R 3.1.0) and sometimes do, eg I have two small pa

[Rcpp-devel] "binding" Rcpp::InternalFunction or Rcpp::CppFunction

2014-08-01 Thread Christian Authmann
Hello, I'd like to do something similar to Foo getdata(DataProvider *p, int id) { return p->getData(id); } DataProvider provider(/* arguments specifying data source*/); RInside R; R["getdata"] = Rcpp::InternalFunction( std::bind(getdata, &provider) ); The idea is that I can export a getter