Is this deterministic or not?

puts “Enter a sentence: "
puts gets.split.sort_by { rand }.join(” ")

takes a sentence and scrambles the words. how is this implemented? i
tried myself first with a for or while loop and tried if word is not
in new_sentence then new_sentence += word etc.
but that could go on for a long time and would be very slow for a
large text.

slix wrote:

puts “Enter a sentence: "
puts gets.split.sort_by { rand }.join(” ")

takes a sentence and scrambles the words. how is this implemented? i
tried myself first with a for or while loop and tried if word is not
in new_sentence then new_sentence += word etc.
but that could go on for a long time and would be very slow for a
large text.

I assume you already know how gets, split, and join work and the
question in your subject refers to sort_by. The sort_by method sorts the
enumerable (in this case, the array of words produced by split) using
the keys generated by the block. That is, sort_by calls the block once
for each element in the array. The block usually (but not in this case)
inspects the element and returns a key. You’re wanting a random sort, so
you use the rand method to return a random number as the key. The
sort_by method sorts the array in increasing order by the random
numbers. Since the keys are randomly generated, the array is randomly
ordered.

Is it deterministic? See my P.S. You can use srand to ensure that rand
returns the same sequence of numbers.

The doc for sort_by is pretty good. Try “ri sort_by”, and “ri
Kernel#rand”.

P.S. I’m sure there’s a lot of good things to be said about PRNGs and
stuff but I’ll let somebody else type it in.

Tim H. wrote:

P.S. I’m sure there’s a lot of good things to be said about PRNGs and
stuff but I’ll let somebody else type it in.

I’ll just add that Ruby’s rand is deterministic, but it uses a very good
PRNG algorithm (Mersenne twister). Unless you really need true
randomness, it’s good enough to use out-of-the-box.

but is the function he is talking about deterministic? i mean rand
could be but he could theoretically guess the same word over and over.

os will this function-execution-time grow according to a formula or it
depends on “how lucky” he is?

2008/6/2 Dave B. [email protected]:

Tim H. wrote:

P.S. I’m sure there’s a lot of good things to be said about PRNGs and
stuff but I’ll let somebody else type it in.

I’ll just add that Ruby’s rand is deterministic, but it uses a very good
PRNG algorithm (Mersenne twister). Unless you really need true
randomness, it’s good enough to use out-of-the-box.

Plus, opposed to other libs and languages, there is a random element in
seeding:

http://www.ruby-doc.org/core/classes/Kernel.html#M001086

Kind regards

robert

On 25.06.2008 19:34, Dave B. wrote:

Robert K. wrote:

Plus, opposed to other libs and languages, there is a random element in
seeding

Well, a combination of the time, the process id, and a sequence number
isn’t actually random! :wink:

However, it’s certainly better than using the time on its own, as has
commonly been done in the past.

Which in turn is even better than using a constant seed - which also has
been done in the past. This was the case I was thinking of.

Cheers

robert

everyoen is missing my point. is the complete method deterministic?
not the rand…

On 28.06.2008 05:51, defn noob wrote:

everyoen is missing my point. is the complete method deterministic?
not the rand…

What complete method? You presented two lines of code and in those the
only potential source of indeterminism is #rand (apart from the user
input), which is precisely why the discussion revolves around this.

Cheers

robert

Robert K. wrote:

Plus, opposed to other libs and languages, there is a random element in
seeding

Well, a combination of the time, the process id, and a sequence number
isn’t actually random! :wink:

However, it’s certainly better than using the time on its own, as has
commonly been done in the past.

Perl has a Math::TrulyRandom module. “The source of the randomness is
from interrupt timing discrepancies.”