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; exposed by load_all(export_all = TRUE) or ::: 3. Not listed in NAMESPACE; only accessible from .Call() I hope this helps clarify the (no) problem. Best, Watal On Mon, Feb 4, 2019 at 10:42 PM Iñaki Ucar <iu...@fedoraproject.org> wrote: > On Mon, 4 Feb 2019 at 13:45, Watal M. Iwasaki <heavy.wa...@gmail.com> > wrote: > > > > 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 undesired in the interactive environment. So > I wondered if by any chance it is possible to control the level of > exposure. It is not a big problem. Good to know the answer is no. > > The "level of exposure" is controlled by the NAMESPACE in a package, > not by Rcpp. And in this case, by devtools. This is what I got from > the function's help: > > export_all If TRUE (the default), export all objects. If FALSE, > export only the objects that are listed as exports in the NAMESPACE > file. > > Regards, > Iñaki > -- Watal M. Iwasaki / 岩嵜 航 SOKENDAI, The Graduate University for Advanced Studies, Hayama, Kanagawa 240-0193, Japan +81-46-858-1576 https://heavywatal.github.io/
_______________________________________________ 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
