I would ask that you rethink using PM as a form of
"parallel processing". If there are obvious resources
that you know about which you have not yet checked, it
saves time for all of us for you to check them first. Based
on experience you will run across just as many unexpected
nuggets, it will save you time, and we will have time and
energy to devote to questions that help people more
directly..
Note that even while deploring the tone of a response to
you I reinforced the basic point that documentation is to
be checked first. The answers that come here are
a volunteer resource. Furthermore the people giving them
are often experienced and qualified professionals. Our
time and energy is likely worth at least what yours is
if we were not choosing to volunteer it, so please treat
it that way. (And our not entirely secret plot is to
infect you with the attitudes, values, and knowledge that
make us able to volunteer so that you turn around and
eventually do likewise. Now please look into this white
light and forget all about this...)
For more on the cultural underpinnings that lead to our
acting this way, I highly recommend Re: Newby Query Comment by
davorg.
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
