I conflated two experiences, work + personal dev, and shouldn't have. At work, it's often the tech manager who is responsible for choosing to ignore errors. In personal dev, it's a free enough world so blame doesn't come into it exactly.

Documentation is for end users, not for the installation process. The end user never sees STDERR so the only chance they get to know something is wrong is if it's included with the document. Like jasonk notes, it can be a clue that the documentation didn't even get built. I'm not looking for blame, I'm looking for confirmation that a software package has some integrity and care applied to it. That process does not start at install/make time. For me it starts at browse-CPAN time. I like knowing a distribution is likely garbage or abandonware before I spend 5 hours finding out by trying to use it in a project.

Again, I love having all the options for errors and development. It really wasn't meant as a rant; maybe an overzealous and somewhat spastic defense of the Pod tools' behavior.

In reply to Re^5: POD ERRORS Hey! The above document had some coding errors, which are explained below by Your Mother
in thread POD ERRORS Hey! The above document had some coding errors, which are explained below by Anonymous Monk

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.