I'd recommend against Devel::Trace, as Devel:: is mostly concerned with hacking the low-level innards of perl, where your module is more of a "userspace" application. Similarly, Debug::Trace implies some close association with the perl debugger, which is not the case here.
If I were releasing this module, I would probably check with the author of Log::TraceMessages first to see if the two modules could be merged or melded into a common namespace: e.g., Log::Trace and Log::Trace::Messages. If there isn't any common ground, perhaps Log::Trace is the best option so far.
For your second module, I reiterate Debug:: and Devel:; as being inappropriate top-level domains Since the module is most closely associated with Test::Harness, perhaps Test::Assertions would be best.
One other place to check naming issues before you upload may be modules@perl.org. See section 2.5 of The Perl5 Registered Module List for details.
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.