> RcppExports.cpp will automatically include a .h that has the same name as > the package and is located in inst/include, iirc.
This is indeed the current solution to the problem of typedefs, however I admin that it's a bit difficult to take advantage of without wading through documentation and/or the mailing list. One alternative we've considered in transposing typedefs (and perhaps using namespace statements) into RcppExports.cpp however this could be considered overly aggressive (e.g. it's theoretically possible this could introduce side effects). J.J.
_______________________________________________ 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
