[R-pkg-devel] CRAN pretest archived because of 2 NOTEs

Gertjan van den Burg gertjanvandenburg at gmail.com
Wed Apr 18 23:47:51 CEST 2018

Unless I'm missing something, I don't think this would work. The random 
numbers are generated in the C library and while I could replace the RNG 
I use now with the RNG from SyncRNG, requiring the users to take action 
for this seems to place an unnecessary burden on them.


On 04/18/2018 10:01 PM, Iñaki Úcar wrote:
> 2018-04-18 22:49 GMT+02:00 Gertjan van den Burg <gertjanvandenburg at gmail.com>:
>> Thanks for your comment. Your suggestion wouldn't solve my original problem
>> unfortunately, because then I'd have to reverse engineer R's RNG for my
>> Python package. Besides, the quality of the random numbers doesn't really
>> matter here, it only matters that they're the same across my packages.
> You could instead write a vignette instructing the user on how to
> replace the default RNG with your SyncRNG. Wouldn't this solve the
> problem?
> Iñaki

More information about the R-package-devel mailing list