The CRAN Repository Policy (revision 4170) states "If running a package uses
multiple threads/cores it must never use more than two simultaneously: the
check farm is a shared resource and will typically be running many checks
simultaneously" and I try to respect this limit in package example cod
On 09.02.2020 09:56, Murray Efford wrote:
The CRAN Repository Policy (revision 4170) states "If running a package uses multiple
threads/cores it must never use more than two simultaneously: the check farm is a shared
resource and will typically be running many checks simultaneously" and I tr
Last week I asked for help with a function name duplication problem. I had
renamed the project and renamed the functions in the project. Example:
needed mvn() from the package MVN, but mvn() is also in thle package mgcv,
from which I needed a different function. Using importFrom, or including
th
Except that the cited wording cannot be literally correct ("never use more than
two") and therefore appears to refer only to the check process. Some rewording
may be needed if the intended meaning is "never default to more than two".
Thanks, Uwe, for your efforts to make me understand.
Murray
___
Hello,
Using package nlme as an example, where there is a registered routine
fit_gnls:
> library(nlme)
> getDLLRegisteredRoutines("nlme")$.C$fit_gnls
$name
[1] "fit_gnls"
$address
attr(,"class")
[1] "RegisteredNativeSymbol"
$dll
DLL name: nlme
Filename: /home/btyner/R-77784/lib/R/library/nl
