Well, actually, I don't think I am assuming that the poster hasn't read the FM; rather, I am suggesting that a post whose answer is obvious -- from the documentation's text or examples (IOW, in the FM) -- strongly suggests that the poster has not RTFMed (or has not RTFMed will diligence). Yeah, that's a lot of qualifiers... almost to the point of making a distinction too fine to worry about...

But you are not the usual poster of what I call 'gimme' questions -- questions that are or are tantamount to "Please write my code for me;" "please do my work for me;" and "I'm ignorant of the existence of the FM." I think the distinction is obvious... and if you post one that falls in the class to which I'm objecting, then I'm going to assume that the issue is a momentary case of brain-lock, not to laziness.

And a request: within the class of well-written docs -- that is, those with decent examples and explanations -- re-examine your last para. Lord knows, I'm as likely or more so than most, to blindspot myself while reading a doc, but (YMMV) find that re-reading a well-written doc ofter provides a face-palm moment when the scales are lifted away.

In reply to Re^5: Put some of the posting guidelines directly above the posting form: by ww
in thread Put some of the posting guidelines directly above the posting form: by TJPride

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.