Quote:
Originally Posted by kogarne  Cutting should always be at random, as so... so should be all ga... nm that.... to each their own...., and to all a good knig...... ,..... post?...? |
First, lol.
Second, cutting IRL isn't random. It's barely semi-random. I know when I cut I make a conscious decision to _try_ to cut at a specific location. I've been known to cut at 1 and 51 on purpose. Cutting at 27 is a bit more difficult to manage, but sometimes I try.
If you were going to be totally anal about it you'd figure out the randomness of the actual cut compared to the intended cut (0 at 1 and 51, maybe +/- 10 at 26, with a slope between) and add a random factor to the intended cut. But given that the deck is sorted pseudo-randomly (or should be) when it's shuffled, unlike a human shuffle, the actual effect of the cut should be negligible if any. You could make cut(int) a noop and nobody'd know unless they read the code.
EDIT: Actually, I've also done a zero-cut (ie accepted the deck as shuffled).