That does make a lot of sense, but it seems to me to go against the common convention. Looking through the OS interface section of CPAN I find names like Unix::Syslog and Schedule::At, and only a very few modules that uses the Uppercase::lowercase schema. I guess this convention is not the be-all-end-all, but I personally know that I would find the name confusing, the reason being that I install a lot of the Perl modules I use via the Debian package management system. So if I saw a package called libunix-lsof-perl and installed it I would then try to look for the perldoc for Unix::Lsof first and only suspect a different capitalization if that failed.

Another reason why I'm not entirely convinced this is appropriate is that the lsof man page itself capitalizes Lsof when it's at the beginning of a sentence, i.e. follows convention. Also, Unix::lsof::Result (which is the object returned from an lsof() run) looks a bit naff, doesn't it? ;-)

But thank you a lot for the recommendation, I do think namespace is one of the most important thing to decide before registering a module, anybody else have an opinion on this?


All dogma is stupid.

In reply to Re^4: RFC: Unix::Lsof by tirwhan
in thread RFC: Unix::Lsof by tirwhan

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.