Displaying 2 results from an estimated 2 matches for "myotherroutine".
2017 Feb 22
0
Registration of native routines
...r and optionally the type for .C/.Fortran.
> - it finds native routines faster, especially if 10s of name spaces are loaded.
Do these benefits also hold for packages that currently use useDynLib
exclusively in combination symbol names? E.g for the example from WRE:
useDynLib(foo, myRoutine, myOtherRoutine)
Which is invoked via:
.Call(myRoutine, x, y)
What ambiguity or pollution is introduced by foo:::myRoutine? Should
manually registering 'myRoutine' in C still be mandatory in this case?
It was nice having the NAMESPACE as the central declaration of
callable C routines. The "R_reg...
2017 Feb 14
6
Registration of native routines
Registration of 'native routines' (entry points in compiled code loaded
into R) has been available for over 14 years, but few packages make use
of it (less than 10% of those on CRAN with compiled code).
Registration has similar benefits to name spaces in R code:
- it ensures that the routines used by .C, .Call etc are those in your
package (without needing a PACKAGE argument).
- it