I guess it would have been nice if you'd have posted a bug report. I realise that sometimes time constraints don't allow for writing up a sensible bug report with all necessary information, but if you really like the module that would have been the way to go IMO.
That's also my reaction to your OP, there are two good ways of constructively criticising a module. If you think it's irredeemably broken or ill conceived you can say so on cpanratings and give detailed reasons. Otherwise, if you think the module is good in principle but is lacking a feature or has a bug you can file a bug report/wishlist on RT and help the author improve it. Your notion of helping users pick the right module is a good one (and the wish of a more reliable quality rating for CPAN modules is often expressed), but ultimately it's more worthwhile to worry about the code rather than the "marketing" (used here in the loosest possible sense).
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan
-
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.
|
