comment on

How do you know which module is "right" for the task? (or wrong for the task)

It would be nice if module authors included an explanation of why their module is better or worse than other modules that provide the same or similar functionality. Or at the very least highlighted the existence of other modules or approaches.

The best example of this that I've seen is Should I use Date::Manip in the Date::Manip docs.

I tried to do something similar with the Writing Excel Files section of Spreadsheet::WriteExcel.

--
John.

See also Rating System for Modules and mirod's suggestion: Module Reviews (again!).

In reply to Re: Perl Monks += TMTOWTDI by jmcnamara
in thread Perl Monks += TMTOWTDI by hacker

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.


There's more than one way to do things
	PerlMonks