> I think single quotes is right because you don't want PHP to escape
> the characters...the escape is for regex, not PHP
In fact, we're neither correct, I was thinking of PCRE, but this is
POSIX regexes which I'm not familiar with.
From the POSIX man pages:
"To include a literal `]' in the list
I think single quotes is right because you don't want PHP to escape
the characters...the escape is for regex, not PHP
On Jan 19, 2008 9:44 AM, Niel Archer <[EMAIL PROTECTED]> wrote:
> Hi
>
> > OK, I don't think I searched the web hard enough. I've not found a
> > definitive explanation, but I thin
Hi
> OK, I don't think I searched the web hard enough. I've not found a
> definitive explanation, but I think the warning has something to do
> with the dash symbols (\-) within the square brackets. Removing them -
> changing them to the regular expression below - removes the warning
>
> '[EMAIL
OK, I don't think I searched the web hard enough. I've not found a
definitive explanation, but I think the warning has something to do
with the dash symbols (\-) within the square brackets. Removing them -
changing them to the regular expression below - removes the warning
'[EMAIL PROTECTED]'
Que
i dont know if im gonna be wrong but, here i go:
you want to call to $_GET['email'] so in you URL should appear something
like this,
[EMAIL PROTECTED]
On Thu, 2008-01-17 at 12:29 +, Dan Stevens (IAmAI) wrote:
> Calling this code with the argument [EMAIL PROTECTED], I'd expect an
> inter
I'm have trouble with some code that I have been following in a book
regarding regular expressions. I'm attempting to validate an email
using a regular expression. Below is a simplified version of the code
which reproduces the problem I'm having:
\n";
if ($result) echo "Email valid";
