I like Smart::Comments but it prints all its output to STDERR. In another project I'm already redirecting STDERR, so I want to be able to instruct my smart output to go elsewhere: usually, to a disk file.

I've forked Smart::Comments and rewritten it, both to permit printing to any filehandle and to address some stylistic issues. This project is incomplete but making good progress. Please see link to current GitHub repository. More work remains.

Originally, I intended to call this 'Smart::Comments::Log'; its working title is 'Smart::Comments::Any'. Some Monks have objected to the latter name as vague. I need to name it finally, change all places where the name appears, and move the GitHub repo before uploading to CPAN.

I began by keeping the new module fully backwards-compatible with vanilla Smart::Comments but I feel this may be too restrictive in future. The project is a major rewrite, a fork, not a patch. I've emailed current maintainer without getting a reply. The idea of releasing this as a new version of Smart::Comments is probably a dead end, even if I thought it wise.

I've aired this naming issue in CB, posted to comp.lang.perl.modules, sent an RFC to modules@perl.org, and sent a couple emails to current maintainer with CC to TheDamian. The silence is deafening.

I'm hostile toward long identifiers, especially those of mixed case. For what it's worth, I don't feel the 'Smart::' top level namespace was an ideal choice; but now, it may be unwise to put the current module anywhere except under 'Smart::Comments::'.

Current ideas include:

I will update this list to include new suggestions.

2010-07-27:

Perhaps I should note that the list above is only indicative. This node exists because I don't especially like any of them.

2010-07-28:

Devel::Comments is the winner.

Development has halted for two weeks as, here and elsewhere, comments have been solicited on the right name for it. An excessive amount of late-night CB time has been consumed. Hundreds if not thousands of dollars have been spent discussing the topic on thousands of machines throughout the entire civilized world.

Summary:

I bow to the consensus.

Note: Contents may change.

In reply to The Module Formerly Known As ::Any by Xiong

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.