Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update RANDBETWEEN #444

Merged
merged 1 commit into from
Oct 24, 2020
Merged

Update RANDBETWEEN #444

merged 1 commit into from
Oct 24, 2020

Conversation

alexeysankov
Copy link
Contributor

To avoid returning of the same value after execution of the same RANDBETWEEN functions in close time

To avoid returning of the same value after execution of the same RANDBETWEEN functions in close time
@tonyqus
Copy link
Member

tonyqus commented Oct 19, 2020

Maybe a time-stamp seed for this rand constructor is better. How do you think about it? However, it's always semi-random in any case

@imil4eg
Copy link

imil4eg commented Oct 20, 2020

@tonyqus Yeah, time-stamp is a good idea. Or, since it's singleton class it's also possible to have just a int value and always increment it.

@tonyqus tonyqus merged commit 2e9a30b into nissl-lab:master Oct 24, 2020
@tonyqus tonyqus added this to the NPOI 2.5.2 milestone Oct 24, 2020
@tonyqus tonyqus mentioned this pull request Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants