The assumption that "xxxxx() works the same way as xxxx() (2)" will mean something is rife in some parts of the docs.
I do not see a problem with that. It's just a reference. Not also that in many cases, it cannot be documented more accurately in the Perl docs, as it will indeed use the xxxx() from your system, and that may be implemented differently on different platforms.

And there are other parts that still go right over my head. Eg. The use of \G (and (?>...) for that matter ) in regexes. If I sit and read the docs and play in my REPL, I can usually, eventually make these constructs deliberately do something of my choosing. Usually. But you'll rarely if ever see me use them to solve real problems. I've simply never found the analogy or example that allows me to assimilate them into my way of thinking.
Sure, but what's the alternative? Write even more documentation? That will make the fraction that's saying there is too much documentation making it hard to find stuff stronger. Or would could just take out a lot of things from Perl (regexes are hard -- remove them. IO is hard -- remove them), moving them into libraries (or modules). But then, if I want C, I know where to get it.
Concluding that an OPs failure to understand the relevant part of the docs is due to a lack of "due diligence", is assumptive in the extreme.
Perhaps. I don't see many questions of the form of "I read 'X Y Z' in the documentation. Can anyone explain what it means, and whether (and how) I can use it to solve problem W'?". If there are parts of the documentation that turn out to be unclear for large groups of people, I'd like those people to be vocal about. If they don't give any indication they've checked the documentation, and they ask a question that can be answered by just quoting from the documentation, I'll assume they haven't checked the documentation.

In reply to Re^7: Put some of the posting guidelines directly above the posting form: by JavaFan
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.