RInside seems to have done the trick! Awesome. I have no strong opinions on how to implement the tests. The only reason why I wanted the embedded R solution is because we use it that way with Python and Julia, and it gives us "raw C++" tests. In the future, we might also have a xtensor-test package, that we can easily use to write tests for all three languages (in C++) at the same time (through metaprogramming).
But we will definitly also add tests in R (as we have done with Python and Julia, too). It would be awesome if you have a chance to add some to your variant. I am going to fix up the C++ tests that I've added to the "big" PR and make sure that at least those we have right now work fine to establish a baseline to work from. Cheers! Wolf 2017-06-12 4:11 GMT-07:00 Dirk Eddelbuettel <e...@debian.org>: > > On 12 June 2017 at 11:22, Romain Francois wrote: > | You might be looking for RInside. > > Exactly correct in the narrow sense of 'how to get R going from C++'. > > On 12 June 2017 at 01:11, Wolf Vollprecht wrote: > | I am trying to run C++ tests from C++ directly. > | It looks like I need to start the R interpreter for memory management > etc. > > The wider, normal sense of the question is, I suspect, how to add unit > tests > to an R package such as your xtensor-r. Give me a day or two and I may > get a > chance to add this to my variant of your project. > > You generally do NOT want force an embedded R interpreter __as any Rcpp > project is already called from R__. Use CRAN as a repository of (as of > today) 1045 example packages. I don't think a single one embeds R for > testing. The RUnit (older, used by Rcpp itself) and testthat frameworks > are > popular. > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org >
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
