Hi Larry, I think we'd be biting off too much to be worth chewing for other character sets. Most uses are going to revolve around characters allowed in URLs. Expanding that, to a degree, perhaps per a additional character list, or character list flag, might not be too far, but things will get interesting once you start requiring whole custom character lists with multibyte chars thrown in.
Of course, random_string(LOTS_OF_FLAGS) might not be all that helpful once you get enough variations involved to require a page of explanatory text to cover them. Paddy On 25 February 2015 at 05:05, Larry Garfield <la...@garfieldtech.com> wrote: > I can see the use for random_string(), but what about character sets? Does > it only generate random characters within ASCCI / low-UTF-8? Wouldn't > someone in Novsibirsk want it to generate a random Cyrillic string? > > That said, I am +1 on the original proposal. It's in the similar vein as > password_hash(): If users have to think, they'll screw up. Don't make them > think. > > --Larry Garfield -- Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
