My two cents on this. Since I'm working on CUDA code, and CUDA for some reason does not like Rcpp I have to have a separate cpp file exclusively for the RCPP_MODULE, that does not include any cuda code. Then things are resolved in the linker. I'll always put RCPP_MODULE in a cpp file for my work.
-Andrew On Mon, Nov 15, 2010 at 7:50 PM, Douglas Bates <ba...@stat.wisc.edu> wrote: > Is there any guidance on where to put RCPP_MODULE declarations in > package sources? I'm working on the assumption of one module per > package but the module itself can contain multiple class or function > declarations. Is one module per package reasonable or would there be > a reason for multiple modules in a package? > > I typically keep class declarations and definitions in separate files, > usually one class per pair of files. To me it seems that the module > declaration belongs in a header file but I haven't looked closely at > what it expands to. Should it be in a header file or a .cpp source > code file? > _______________________________________________ > 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 > _______________________________________________ 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
