[Rcpp-devel] Export only C function symbols?

[Watal M. Iwasaki]

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.

Best,
Watal


On Mon, Feb 4, 2019 at 11:31 PM Iñaki Ucar <iucar at fedoraproject.org> wrote:

> On Mon, 4 Feb 2019 at 14:59, Watal M. Iwasaki <heavy.watal at gmail.com>
> wrote:
> >
> > 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()
>
> Compiled functions are only accessible from .Call if you don't use
> symbol registration (see 5.4 Registering native routines). But AFAIK,
> this is required by CRAN, and thus Rcpp automatically generates symbol
> registration for you.
>
> 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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20190204/bb47a734/attachment-0001.html>