I disagree. Perlmonks can be a bug report if the author happens to be a monk, and happens to have the time to look at it. YMMV. TMTOWTDI. TTFN.

PS: it's called "attitude". You can be positive or you can be negative. There's no requirement to be positive and a pushover. Not that there's a requirement to be positive. But not only will it help you get what you want (bug reports in a place you can keep track of it), it may get you stuff that you'd really like (help, patches), and it surely will help your blood pressure. Calm down already!

In reply to Re: AUTHORS DO NOT SEE ANY OF THIS by Tanktalus
in thread Module::Build users -- please use the "traditional" create_makefile_pl option by perrin

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.