First off, I agree with the first sentence of your last paragraph. And it wouldn't hurt to provide multiple WTDI in the module itself if you forsee them useful to a large segment of your users (if you have a pretty good idea lots of people want it, and it "fits" within your module's domain, then you're tactically circumventing a lot of reinvented wheels).

What I *would* suggest for your specific module, is to make the simplest case the default one. You're mimicking command line calls, so it's best to not "expect too much" from your implementations. So, IMHO, fgrep gets to return the array of matches, fgrep_hashref gets to return the AoH with the extra meta information.

In reply to Re: KISS vs Feature set by AidanLee
in thread KISS vs Feature set by Masem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.