AND NO ONE THINK IT'S NEEDED - at least comments to my question say so......... "Yeah, why you think you need reliable email parser, what you will use it for? Forget about it, man, you don't need it. Nobody need it!" :(
I think you need to re-read the replies a bit harder. They mostly boil down to "Try module X or Y; if those don't work contact the maintainers with test cases which exercise the problems you think there are".
- davorg: "And if they don't, then the project members seem pretty open to receiving bug reports and patches."
- davorg: "If you have specific areas where you know the existing modules have problems, then why not get involved with the Perl Email Project and help them fix those problems."
- dave0: "Well, given that I use quite a few of those modules on a daily basis, I find it hard to believe that they're all "far away" from compliance. Do you have any specific issues to point out?"
They're not saying live with the bad software, they're saying if you've got problems show how to reproduce them and let the maintainers fix them. If they don't, you're free to put your own überperfect code up on CPAN to shame them in the glorious open source meritocracy that it is.
-
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.
|
