compileAttributes and use of .External2() for calling native symbol routine about rcpp

[eddelbuettel]

Hm. A guess from the hip here -- are you sure it's

• not the .External2 ?
• not also happening via the base R function [1] writing src/init.c as we IIRC call it to?

[1] ie tools::package_native_routine_registration_skeleton() ?

[astamm]

Thanks for the reply. And apologies for filing the issue here. It actually happens when tools::package_native_routine_registration_skeleton() is invoked. Not sure why yet. But seems unrelated to Rcpp.

[eddelbuettel]

No worries. You interfaced our function, I just happened to suspect that the base function was at the heart of it.

I to have written simple wrapper around uniroot() and I got by without .External2(). I am sure you find a way that is compliant with the R API.

[astamm]

Actually it seems that the problem is in tools:::native_routine_registration_db_from_ff_call_db() at the beginning when they define the vector ff_call_names to look for in the code.

It is currently:

native_routine_registration_db_from_ff_call_db <- function (calls, dir = NULL, character_only = TRUE) 
{
  if (!length(calls)) 
    return(NULL)
  ff_call_names <- c(".C", ".Call", ".Fortran", ".External")

if I add .External2 to the vector, it works fine.

[eddelbuettel]

Wrong repo. We do not have control over the tools package. 😉

[Enchufa2]

@astamm FWIW, the manual page for .External2 declares it as an internal version of .External, which suggests that you probably should be using .External instead. Of course this collides with the fact that they export it. So... who knows.