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.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.