On 12/28/2005 3:01 PM, Duncan Temple Lang wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Coincidentally, I am in the process of working on a related aspect of
> symbol resolution.
>
> The issue is likely to be the caching of native symbols
> that we do. We do not cache the registrat
Duncan Temple Lang wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Coincidentally, I am in the process of working on a related aspect of
> symbol resolution.
>
> The issue is likely to be the caching of native symbols
> that we do. We do not cache the registration information,
> jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coincidentally, I am in the process of working on a related aspect of
symbol resolution.
The issue is likely to be the caching of native symbols
that we do. We do not cache the registration information,
just the address of the routine. And so the tes
The R_registerRoutines C function allows the number of parameters to a
.Call function to be registered. For example, the tools package
function md5sum() calls "Rmd5", which has been registered to require
just one parameter.
But if it is called with the wrong number of parameters, only the first
e
