Where are your doc patches? Where is the work you've put into it? How can you demand things of and complain about the work people do on a volunteer basis?
Besides that, your laundry list of complaints doesn't address his comment at all: he said the Perl documentation is better than any he had see before. Putting aside the impossibility of proving what he has or hasn't seen before, it was a comparitive analysis. Your complaints about the quality of the documentation may indeed be correct (and I'm not saying they are; they sound a bit too much like pissy ranting for me to take seriously), but that's completely missing the point.
Now, I'll make a prediction: your response (if you respond at all) is going to be even less relevant and coherent than your original rant. So go ahead, give me your best shot, but I'm not going to be surprised.
-
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.
|
