I believe Dr. Ripley said that the UseDynLib doesn't address the
middle two points of the list.
I experimented with the Delaporte package timing calls using both
methods, and they were within 1~2 microseconds of each other using
microbenchmark. Since the more complicated way is now expressly
prefe
On Tue, Feb 14, 2017 at 5:25 PM, Prof Brian Ripley
wrote:
>
> 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 avoids polluting the search space for native
On 2017-02-19 09:19, Prof Brian Ripley wrote:
On 14/02/2017 16:25, Prof Brian Ripley wrote:
Registration of 'native routines' (entry points in compiled code loaded
into R) has been available for over 14 years,
...
(There are reports that the check in 'R CMD check' on Windows sometimes
fails
On 14/02/2017 16:25, Prof Brian Ripley wrote:
Registration of 'native routines' (entry points in compiled code loaded
into R) has been available for over 14 years,
...
(There are reports that the check in 'R CMD check' on Windows sometimes
fails to detect use of registration. This is being l
On 14/02/2017 17:28, Avraham Adler wrote:
On Tue, Feb 14, 2017 at 11:25 AM, Prof Brian Ripley
wrote:
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 compile
On Tue, Feb 14, 2017 at 11:25 AM, Prof Brian Ripley
wrote:
> 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 b
