I'll try not to echo the other answers with respect to fishing and fish and eating and catching fish.

I agree that it's sometimes frustrating to get a reference to an answer instead of an answer. My favorite answers are those that include the reference and a quick explanation of what you are looking for or will likely end up with. This way I don't have to wade into the docs completely clueless. Sometimes, however, the answer is best explained by the docs.

Sometimes the docs really stink. Really. I have at least $125 worth of O'Reilly books which I use to supplement perldoc.

I agree that sometimes it's hard to find good programming tutelage in perldoc (except for perlboot, this is a shining gem among POD). The POD is mostly a reference to functionality, in spite of some great explanatory sections.

The questions least likely to get RTFM as responses are the ones which indicate that you've tried to find relevant bits in the FM and couldn't. Or show that you've read the FM but still have a question about xyz piece because the FM is Fing Obscure (see File::Find).

As for RTFM, it's not a bad thing. It's a good thing. At least there is a FM.{grin}

In reply to Re: RTFM by ichimunki
in thread Lies Der Verdammten Buch! (RTFM) by locked_user mr_leisure

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.