search for: user_unif_rand

Hi, When loading a package that provides the user-supplied RNG hook user_unif_rand, calling getNativeSymbolInfo("user_unif_rand") returns informations about the loaded symbol. I am using this to identify which package currently provides the RNG hook. The results are the same on windows and linux if only one library provides the hook. If one loads a second package tha...

Hi Everyone, I did a quick search of the list and it looks like this may not have been asked before... I'm trying to generate a matrix of random numbers between 0 and 1, with 6 columns, 10000 rows. About all I know is that runif(1) gives me the random number I'm looking for. Any help would be great! thanks, -Max

Hi Everyone, I did a quick search of the list and it looks like this may not have been asked before... I'm trying to generate a matrix of random numbers between 0 and 1, with 6 columns, 10000 rows. About all I know is that runif(1) gives me the random number I'm looking for. Any help would be great! thanks, -Max

...of R to run their own generator in R. However, there is no such mechanism for package writers. Those who want to add their own generators abuse RNGkind(kind="user-supplied") for their purpose. The problem with this approach is that it relies on the unique existence of the function "user_unif_rand". When two packages are loaded that use this interface, then at least one package is broken. If the user herself loads a shared library that contains such a function, some of the functionalities of all the corresponding packages are broken. When writing my paper I found the following package...

...ntly similar. A relatively compact (but still brittle) way to match function declarations in C header files is shown at the end of this message. I have confirmed that compared to tools:::getFunsHdr, the only extraneous symbols that it finds in preprocessed headers are "R_SetWin32", "user_unif_rand", "user_unif_init", "user_unif_nseed", "user_unif_seedloc" "user_norm_rand", which are special-cased in tools:::getFunsHdr, and the only symbols it doesn't find are "select" and "delztg" in R_ext/Lapack.h, which we should not be f...

...atively compact (but still brittle) way to match function > declarations in C header files is shown at the end of this message. I > have confirmed that compared to tools:::getFunsHdr, the only extraneous > symbols that it finds in preprocessed headers are "R_SetWin32", > "user_unif_rand", "user_unif_init", "user_unif_nseed", > "user_unif_seedloc" "user_norm_rand", which are special-cased in > tools:::getFunsHdr, and the only symbols it doesn't find are "select" > and "delztg" in R_ext/Lapack.h, which we...