Usually, it only becomes apparent after some discussion and analysis of the user-code and the module-code that there is a bug in a module. And then we encourage the original poster to open a ticket on RT.
In the case of long standing bugs, there either are already open RT tickets (see Problem with Archive::Tar created archives and Winzip for example) or the bugs will never be fixed due to P5P (see Problem with Find for example) and people have given up.
It's rare that people come here with a bug report. It's even rare that people come here with self-contained code and data on the first try. People often blame modules for faults in their own code. If people opened bug reports for every question they have, you would be here bitching about how people misuse RT to ask questions. I think opening an RT bug is at the end of a discussion at best, and not at the beginning.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|