You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We have bundled our own Drand48 for a long time. We should not have any logic in Configure regarding this as it is redundant.
We probably should get rid of randbits and RANDBITS as well. I cant see any use of them that isn't a bad idea.
This also applies to srand48, and random and srandom. Basically Configure shouldnt be concerning itself with random functions from the OS, it should just hard code the internal implementation we provide.
Steps to Reproduce
N/A
Expected behavior
Configure shouldnt probe for Drand48 or any other RNG.
Perl configuration
This is true as of perl 5.41.9 at least.
The text was updated successfully, but these errors were encountered:
I've spent too much time in Configure lately, so I totally understand. RANDBITS is a relic and can (and should be) removed. I think this needs to stay:
drand01="Perl_drand48()"
I can't find the reference right now, but I believe some compilers take drand01 as a compile time override for the internal C rand() function. Not sure we if we use that but we might want to investigate.
Description
We have bundled our own Drand48 for a long time. We should not have any logic in Configure regarding this as it is redundant.
We probably should get rid of randbits and RANDBITS as well. I cant see any use of them that isn't a bad idea.
This also applies to srand48, and random and srandom. Basically Configure shouldnt be concerning itself with random functions from the OS, it should just hard code the internal implementation we provide.
Steps to Reproduce
N/A
Expected behavior
Configure shouldnt probe for Drand48 or any other RNG.
Perl configuration
This is true as of perl 5.41.9 at least.
The text was updated successfully, but these errors were encountered: