in reply to How do you decide to use a module from CPAN or not?

I mentioned this somewhere vaguely, I myself:
  • 0 I rely upon the module name or the *.readme, and secondarily the README or pod if using .*search.cpan.org
  • 1 Is it supposed to do what I want? skip to 3
  • 2 Is it related to what I want? (Could I rethink my strategy to make use of it)
  • 3 Does it work? skip to 5
  • 4 Can I make it work, or cajole the author into doing so?
  • 5 I use it.
  • * And finally, is it just plain cool and likely to be something I'll use if it's laying around? (I'm a packrat, there's a reason I have 300k of bookmarks even after pulling out most of the software
  • I frankly don't care about the API, as I much as I dislike OO if it works I'll take what I can get, same goes for support (excluding step 4) and maturity.

    --
    perl -pe "s/\b;([st])/'\1/mg"

    • Comment on Re: How do you decide to use a module from CPAN or not?