Hello Corion...the idea to upload a bug report is something I came up with while typing the idea into the textarea. I had not thought the idea through. I do check new, open, and resolved issues before reporting a bug. If the same bug is already reported, I usually just tack my name onto the original bug report.
The only thing I know about installing modules is I must type cpan Module::Name at the command prompt. I do not know how to read the output. I have only gotten as far as writing .pm files, since none of my work is really sharable or possibly interesting enough to be CPAN worthy. Tests are still a complete mystery to me. The last time I looked at one of the Test modules, I got lost and left it alone. I have not written a module yet which I could automate any of the testing. I have to eyeball everything. So when it comes to module tests during installation, I have not a clue what to look for in the results.
I promise to be as good a girl as I can be when reporting bugs when I get won't install without force.
Have a cookie and a very nice day!
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||