There was a time when I read every single post at PerlMonks. My personal experience has been that the majority of folks are either happy to find out that the problem is not in their code or to use what ever work around results in their posting. No matter how easy you make it, most folks will just not report the bugs.
So how can PerlMonks help? It would be a start for regulars to encourage posters to file bug reports in their replies. Some already do. We could add a shortcut to [RT://Module::Name]. I think this is a fine idea. We could open the ticket on the behalf of the person asking the question if our gentle encouragement falls on deaf ears. I think this is unrealistic.
The problem exists in all perl forums that I visit regularly (PerlMonks, #perl on freenode, use.perl, the perl community on LiveJournal, etc). I hope your education extends elsewhere as well. I will try and be better at encouraging folks to file bug reports.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||