Search Archives

Hi all, Adding `[[Rcpp::export]]` tag to a package function leads to the following outcomes: 1. Definition of "RcppExport SEXP _mypkg_myfun()" in RcppExports.cpp (hence in dll) 2. Definition of "myfun() {.Call(`_mypkg_myfun`)}" in RcppExports.R It is...

Hi all, I have been working on an R interface package to a shared library written in C++. It works almost perfectly, but the output to std::cout is not shown on R console (on Linux). Of course Rcpp::Rcout...

Dear I?aki, The registration is fine. Besides that, Rcpp creates RcppExports.R and defines wrapper R functions to .Call registered functions. My question was how to prevent it. Post-processing RcppExports.R is a possible workaround suggested by Dirk...

Hi all, I have been trying to make an R function to call my C++ simulation program in this way: ```c++ // [[Rcpp::plugins(cpp14)]] #include <Rcpp.h> #include <mylib.hpp> // [[Rcpp::export]] std::string run_simulation(Rcpp::CharacterVector args=Rcpp...

Dear Dirk, Is it possible for Rcpp to do some pre-execution hook before user code? For example, if Rcpp system can hijack the std::cout buffer by executing `std::cout.rdbuf(Rcpp::Rcout.rdbuf())` automatically, then Rcpp users (and...

Dear Dirk, Thank you for the prompt answer. Currently all the C++ functions with [[Rcpp::export]] tag are exposed to me by `devtools::load_all()` in the dev process. But some of them are only useful in other functions and...

Dear I?aki, Thanks for the comments. But I know the switch you mentioned. The levels I was talking are within the unexported functions. Here are my imaginary levels: 1. Listed in NAMESPACE; always visible 2. Not listed in NAMESPACE...

Thank you for the quick and kind reply, Kevin! You are right. I confirmed that the program option object is defined as a local variable in mylib::Simulation constructor, and is destructed correctly. But I found that the object is...

Yes, escaping from the check seems difficult. I have created a quick PR on this for further discussion. Watal On Sat, Oct 27, 2018 at 2:13 AM Dirk Eddelbuettel <edd at debian.org> wrote: > > Hi Watal, > > Thanks for being...

Dear Dirk, Thank you for the prompt response. Good to know there is no easy way. I have made up my mind to change the library code as you suggested. But I don't like preprocessor macro; therefore, the problem...

Dear Dirk, Sorry for my poor explanation. I have read `inst/include/Rcpp/iostream/Rstreambuf.h` and think I understand the role of Rcpp::Rcout, but failed to explain my point. By "users [...] can just stick to std::cout", I...