Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61378
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <500592AE.4060305@gmail.com>
References: <CAF+90c9c-LuEzXyWJYfkQ5ycNYYRTqBB+0NhZDEkhGeQQaeEpw@mail.gmail.com>
	<CAN+gjSe7OR2S0gUON27_thx4dPPvsnj_24a4dxfieL_0mzvFZg@mail.gmail.com>
	<CAAyV7nHz_0HEV3_E2qJzYMvKUZUzz3vui-2vHZbH=hu3wBLXSQ@mail.gmail.com>
	<CAKZjf5SUR_Tt4Y4jwK2oYgYusBq4dGvQ75YLOOf8J=kDD=nmDw@mail.gmail.com>
	<5004775D.601@gmail.com>
	<CAKZjf5R16k5MJ=EUZggX+E5mUjsV0Bqm-9oaEby-hhbfQsWiig@mail.gmail.com>
	<500592AE.4060305@gmail.com>
Date: Tue, 17 Jul 2012 22:00:51 +0200
Message-ID: <CAKZjf5R8=Zy2Ntz_rK+ZMO3ZOWXLrRa-CZAHfPf+F7_XgsiErw@mail.gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, Andrew Faulds <ajfweb@googlemail.com>, 
	Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: =?ISO-8859-1?Q?Re=3A_=5BPHP=2DDEV=5D_Random_string_generation_=28=E1_la_passwo?=
	=?ISO-8859-1?Q?rd=5Fmake=5Fsalt=29?=
From: alex.aulbach@gmail.com (Alex Aulbach)

2012/7/17 =C1ngel Gonz=E1lez <keisial@gmail.com>:
> Those could be in the flag. The / are not really needed, they are an
> additional syntax over regex provided by PHP (and the character can be a =
different

makes it a little bit like Perl. I see this as a "standard". So for me
a regex is with delimiters, even if the lib doesn't need them.

> one, although usually / is picked).

Think, it comes from SED. I usaly use '#' - better visibility. :)


> The above code doesn't support POSIX character classes, just picking
> characters out of a string (which I agree is simple).

PCRE uses the Posix classes...

[btw. off topic: I read thrugh http://www.pcre.org/pcre.txt - meiomei,
they have introduced things here... "backtracking control", "path
recording"... incredible]


>> // Search spacer strings
>> strpbrk ("Hello World", str_charset('/[\s]/'));
> So you're expanding all spacing characters, then iterating over them
> with strpbrk(),
> a preg_match() would have been more efficient.

Of course. Every example could be done more efficient with regex. It's
not the point! Once used, str_charset() is "ready", the result can be
cached and reused for much more things. And then it's faster than
pcre, even ready compiled.

Hm.


Maybe back to the roots? Using range() is not so complicated:

implode('',
     array_merge(
             range('a','z'),
             range('A','Z'),
             range('0','9'))
     ))

<shrug> So I think, if we don't need charset-encoding, we won't need
this special functionality.

--=20
Alex Aulbach