in reply to When is it better to NOT release a new module?

The problem is, it solves the same problem as a half-dozen other modules do: How do you simply, quickly and elegantly parse named parameters passed to a function/method?
The fact that half a dozen other modules do the same thing means that those modules solve the problem poorly in some peoples opinion. In fact, enough people found the solutions poor that the module got re-invented over and over again.
But is that enough to justify yet another module solving the same problem?
I don't understand the question. You already created the other module, and you like it - so it *did* justify another module. Otherwise, you wouldn't have done it (or not have liked it). Put it on CPAN. It only takes a single other person to like it for justification.
Perl --((8:>*
  • Comment on Re: When is it better to NOT release a new module?

Replies are listed 'Best First'.
Re^2: When is it better to NOT release a new module?
by bluto (Curate) on Nov 02, 2005 at 19:01 UTC
    The fact that half a dozen other modules do the same thing means that those modules solve the problem poorly in some peoples opinion. In fact, enough people found the solutions poor that the module got re-invented over and over again.

    Perhaps it's just another manifestation of caring about the color of the bikeshed. The sheer number of config file parsers on CPAN proves this is a primal instinct. :-)