But there's a barrier for posting correction posts: they are often awarded with negative reputation.

I don't find this to be generally true, but maybe it depends on the tone of the answer. Correction posts which insult the author or disparage his ability to program seem less well accepted than those which simply point out the mistake. I would construe this as a feature of the PM system rather than a bug though, because civility can be more important than content.

And I also think that a chance at receiving negative votes should not prevent one from posting content that one thinks appropriate, just as the chance of receiving upvotes should not be the only reason one posts (wow, lookee here, full circle to the OP ;-). Personally I've learned a great deal from answers which correct mistakes or misunderstandings in nodes that I wrote, and I think it'd be a shame if people held back on constructive criticism just because they think it may be unpopular.

But claiming gravity doesn't exist isn't a "point of view". It's plain wrong.

Unless gravity really does not exist in your frame of reference because you're a CGI script. :-)


A computer is a state machine. Threads are for people who can't program state machines. -- Alan Cox

In reply to Re^7: To help not to misguide by tirwhan
in thread To help not to misguide by c_chipster

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.