Ok, I'll try to be not as evasive anymore ;-). But the point still stands that ultimately the job of assessment falls to the only person who knows where the juwels are, to you. Only you can judge if for example some test scripts are worth keeping or not
moritz answer is already 90% of what I would have to say. Normally you should not include unfinished code experiments, non-working test scripts or utilities that are only relevant to your mode of operations
BUT there are always exceptions. Your example of a test script that almost works and is useful and you just don't know how to make it work could be such an exception. You might put it in (disabled naturally) with a plea to help make it work.
Or there might be a utility script that is really useful for this module. I have no idea what that could be with Devel::Comments, but for example for a module simulating a game world it could be a fight simulator script to aid in balancing
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.