Well i put this little baby together for a project of my im working on, and thought i share it with you all.

Not the moast advanced but does what i wanted.
There´s room for alot of improvement i would guess.

Have fun :)

__________________
Of course the whole point of a doomsday machine, would have been lost if you keep it a secret.

Very cool.

__________________

Thx. Village Idiot :)

__________________
Of course the whole point of a doomsday machine, would have been lost if you keep it a secret.

Nice script, thanks for sharing.

One thing however, there is a mistake, the script generates a 'undefined offset' because you have set the max value of mt_rand to '62' (number of elements in the array) so every now and again you will get the '62' being produced and used as a key for the array, however the maximum array key value is only '61' (php is zero indexed so the first value is 0 not 1) thus the key '62' doesn't exist.
to rectify just subtract 1 from the max value of mt_rand

that should now run correctly.

apart from that its nice, thanks m8.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

@sketch media

Thx. I just tought of that little misstake myself :)

It botherd me when i went to bed lastnight. Cause there were something i missed in the code. And that might be it.

Thx for reminding me :)

__________________
Of course the whole point of a doomsday machine, would have been lost if you keep it a secret.

I would advise making the function somewhat more efficient. There are a number of things which, unless you can justify their inclusion or the way they've been done, I feel are useless or could be better implemented.

First, the method of constructing the array of characters which can be used in the generated string. You make four function calls (range, array_merge) simply to construct a single array of characters a-zA-Z0-9. This array will always be the same upon every function call so why not just hard-code?

Next, the for/shuffle lines. What advantage does shuffling the array 5, 10, 50 times have over doing it once? Does it make the array more random? I'd say this whole section is unnecessary since you're later choosing array keys at random anyway (with mt_rand).

I'd also suggest returning the resulting string rather than echoing out each character as the function will be much more versatile (who says you need to output the string?).

Sketch, thanks for the note about the off-by-one error on $len however you introduce one yourself by changing the final for loop to use intval($passLen-1) (the resulting random string will always be one character less than $passLen).

I think this function could well be refactored into something maybe 10 times faster to run and equally so easy to glance at and understand what's going on.

Its not an undefined offset, but yes thanks for noticing that, i didn't mean to post the code with that line in, i must have left it in when i was messing with the code earlier no idea why mind but there you go.

note to self: learn how to use copy and paste properly

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

Your right. There are plenty of things that could be done in another more effective way.

This how ever were just a short bare bone code snippet that anyone could base there random string functions upon if they wish. I wasn't out to publish a complete solution, just another way to do things. Maybe not optimal but it works.

The reason i used the approach with the range() to get chars into arrays and then merge them was to be able to add other ranges() or manually constructed arrays with chars to mix with.

And maybe the shuffle() is´nt necessary.
But advantage you say ?, it makes the array more random.
And when you later down the code pick random chars.
Well that's just more random candy for ya :)

I little sharing if you like.

i admit that i should of course have made the function return the string and not echo().

This optimal performance hysteria goes to far some times.
Hardware these days can do a lot more then we tend to give it credit for. And of course it´s also a question of how often one use the said function.

To conclude. I appreciate your insight and shall remember it in future adventures.

/Eye

__________________
Of course the whole point of a doomsday machine, would have been lost if you keep it a secret.

Perhaps, but in my opinion it doesn't mean that you shouldn't optimize everything you do.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

I'm not really talking about optimising the code, in the sense of squeezing out that last microsecond of runtime, or saving that extra CPU cycle here and there. My main point was that much of what you wrote appears to have been unnecessary for the functionality of the code. Case in point, the multiple calls to shuffle.

From my understanding (which may be wrong!), shuffling an array multiple times doesn't make the values inside it any more randomly placed than simply shuffling once -- I'd be happy to see any tests done to determine the actual behaviour, if indeed the array is 'more random'. Because of that, I feel that shuffling more than once isn't necessary. Indeed, the entire point of shuffling the array (to randomise the values) is a non-point because the values are selected at random later using mt_rand. What's the advantage of selecting a random value from a shuffled array over selecting a random value from an ordered array? I don't see any, maybe you do.

I'll repeat, I'm not looking to optimise the code for ultimate performance but instead trying to get across the idea of good practises. There's no good point that I can think of (feel free to point any out!) as to why it's a good idea to shuffle the array once, twice, twenty times.

Take out the code block under "shake it around abit" and does the function perform any differently? Are the echoed/returned strings any less random?

I got ya ;)

I see what you mean.
It would be best to remove the shuffle() thing.

I guess i just was a happie coder getting a little crazy burning the midnight oil :)

__________________
Of course the whole point of a doomsday machine, would have been lost if you keep it a secret.