For Programmers: Free Programming Magazines  


Home > Archive > PERL Modules > July 2004 > Choosing a good namespace for a module to upload to CPAN









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Choosing a good namespace for a module to upload to CPAN
Peter Corlett

2004-07-14, 8:56 am

I have a handful of interesting little modules that I want to upload
as my first contributions to CPAN. I already have the PAUSE account,
but note the comments on choosing the right namespace and have looked
at the Perl 5 Module List.

One module I have is locally called SCSI.pm. It's a module for
direct-access to SCSI devices. It's intended to support access on
multiple platforms, but I've currently only written a Linux backend.
(I've also got a CDDA ripper by way of example.)

Were it Linux-specific, I'd be tempted to go for Linux::SCSI, but the
API is intended to be more generic. Device::SCSI seems fitting and
keeps it out of the top-level namespace, but I note there's enough
oddball items in the top level to suggest that plain SCSI.pm could be
just fine.

Comments, anybody?

--
PGP key ID E85DC776 - finger abuse@mooli.org.uk for full key
Sherm Pendley

2004-07-14, 3:57 pm

Peter Corlett wrote:

> API is intended to be more generic. Device::SCSI seems fitting and
> keeps it out of the top-level namespace, but I note there's enough
> oddball items in the top level to suggest that plain SCSI.pm could be
> just fine.


I'd use Device::SCSI. As you said, there are enough oddball items at the top
level - no need to add more.

sherm--

--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com