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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|