in reply to RFC: Unix::Lsof

This is a nice module. I had an harmless error while testing on my Slackware 12.0 box ( perl is a symlink to perl5.8.8 ): 
emmanuel[~/temp/Unix-Lsof]$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl5.8.8 "-MExtUtils::Command::MM" "-e" "t
+est_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/10.procedural.......ok     
t/20.lsof-result......1/55 
#   Failed test 'Correct command name'
#   at t/20.lsof-result.t line 75.
#          got: 'perl5.8.8'
#     expected: 'perl'
t/20.lsof-result......54/55 # Looks like you failed 1 test of 55.
t/20.lsof-result...... Dubious, test returned 1 (wstat 256, 0x100)
 Failed 1/55 subtests 
t/pod-coverage........ok   
t/pod.................ok   

Test Summary Report
-------------------
t/20.lsof-result.t (Wstat: 256 Tests: 55 Failed: 1)
  Failed test:  23
  Non-zero exit status: 1
Files=4, Tests=71,  2 wallclock secs ( 0.05 usr  0.01 sys +  0.63 cusr
+  0.64 csys =  1.33 CPU)
Result: FAIL
Failed 1/4 test programs. 1/71 subtests failed.
make: *** [test_dynamic] Erreur 255

[download]

Replies are listed 'Best First'.
Re^2: RFC: Unix::Lsof
by tirwhan (Abbot) on Feb 26, 2008 at 18:42 UTC

    Thanks! I fixed the test to pass on your platform as well and uploaded. Since nobody seems to object to the name I think I'll register a namespace tomorrow and upload it to CPAN.


    All dogma is stupid.
[reply]
[d/l]

      Though I prefer Unix::lsof (no, it doesn't look like a pragma, there is a capital 'U' -- at least that is the only motivation I could imagine for one capitalizing the 'l').

      - tye        

[reply]

        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.
[reply]
[d/l]
[select]

In Section Meditations