Re: Please evaluate: RegEx for validating e-mail addresses

I also recommend the "it's too frickin hard so let it be" approach. For most of the stuff I do, I allow the email to be semi-arbitrary and then if the user doesn't get his confirmation mail, etc, it's his responsibility. The UDP nature of email makes it ultimately impossible to trust 100% anyway, so I don't feel bad just handing the user input over to the mail stuff.

Although, surely someone has taken a crack at validation with Parse::RecDescent or somesuch? I'd love to see it if someone's done it.

Comment on Re: Please evaluate: RegEx for validating e-mail addresses

Replies are listed 'Best First'.
Re^2: Please evaluate: RegEx for validating e-mail addresses by FoxtrotUniform (Prior) on Sep 25, 2004 at 21:17 UTC
Although, surely someone has taken a crack at validation with Parse::RecDescent or somesuch? I'd love to see it if someone's done it. We were just talking about that in the CB. bart pointed out that Parse::RecDescent would probably be way too slow. Parse::YAPP might be better (see Re:x2 Easy Things (a plug for Parse::YAPP)) if you want a pure-Perl solution, but for speed there's no reason not to build a parser with yacc or bison or something of the sort and XS it. Incidentally, I googled for an RFC822 yacc grammar (I can't believe that nobody's distributing one; it seems like the obvious thing to do) and came across this article. It's rather old, but probably still applies. `-- F o x t r o t U n i f o r m Found a typo in this node? /msg me % man 3 strfry`	[reply]

Replies are listed 'Best First'.

Re^2: Please evaluate: RegEx for validating e-mail addresses
by FoxtrotUniform (Prior) on Sep 25, 2004 at 21:17 UTC

Although, surely someone has taken a crack at validation with Parse::RecDescent or somesuch? I'd love to see it if someone's done it.

We were just talking about that in the CB. bart pointed out that Parse::RecDescent would probably be way too slow. Parse::YAPP might be better (see Re:x2 Easy Things (a plug for Parse::YAPP)) if you want a pure-Perl solution, but for speed there's no reason not to build a parser with yacc or bison or something of the sort and XS it.

Incidentally, I googled for an RFC822 yacc grammar (I can't believe that nobody's distributing one; it seems like the obvious thing to do) and came across this article. It's rather old, but probably still applies.

-- F o x t r o t U n i f o r m Found a typo in this node? /msg me % man 3 strfry

[reply]