Hi, Jacob.
Generally speaking, namespace registration is getting rarer as people
seem to find modules via search at search.cpan.org or other places
rather than the namespace tables.
That said, the convention of a good namespace prefix still holds
whether or not you formally register and helps people find modules
they otherwise might miss. I did a quick search for "column report"
and saw things like "Text::Report", "Data::Report", "Data::CTable" and
"Data::Presenter". From that sample, "Data::" is probably a good
prefix, but I think "Text::" is also a good option since your modules
focuses on the output more than the input.
I would encourage you to consider a more descriptive name than
"UNLreport" -- since I don't know what "UNL" means. The
module-auth...@perl.org list is a good place to ask for feedback on
names, as is perlmonks.org.
If you do add a prefix, you'd move your module file to (for example)
"lib/Data/UNLReport.pm" and change the package line to "package
Data::UNLReport". Then it would be loaded via:
use Data::UNLReport;
While you may "fear" that extra length, it's very typical for CPAN
modules to have a prefix. While there is no rule against a
"top-level" namespace, people are usually encouraged to avoid it
unless their work represents an entire project or family of modules.
C.f "Moose".
Regards,
David Golden
On Wed, Mar 2, 2011 at 1:12 AM, Jacob Salomon <jakesalo...@yahoo.com> wrote:
> I was about to request a namespace so that my new module could be more
> easily found in a search.
>
> The application page suggests I "try to suggest a nested namespace that is
> based on an existing root namespace". All fine and well but I seem to be
> unable to find a list of existing namespaces. Looking at the list of
> modules under 'String_Language_Text_Processing" I could hazard a guess that
> my module could fit under "Data::", although I have not defined it as such -
> it was written to stand on its own. i.e. use UNLreport;
>
> My main question is: Where do I find a list of existing namespaces so that I
> can see where to shoehorn my module?
> The secondary question might be: If I do request a namespace like
> Data::UNLreport, how will users access it?
> use UNLreport; # As I have it written now
> or
> use DATA::UNLreport? # As I fear (well, a strong word) it might become
> required
>
> Thank you for clarifying this for me
>
> - Jacob Salomon
>
> ________________________________
> From: PAUSE <upl...@pause.perl.org>
> To: jakesalo...@yahoo.com; andreas.koenig.gmwojprw+pa...@franz.ak.mind.de
> Sent: Tue, March 1, 2011 11:28:04 PM
> Subject: PAUSE indexer report JASALOMON/UNLreport-1.02.tar.gz
>
> The following report has been written by the PAUSE namespace indexer.
> Please contact modules@perl.org if there are any open questions.
> Id
>
> User: JASALOMON (Jacob Salomon)
> Distribution file: UNLreport-1.02.tar.gz
> Number of files: 7
> *.pm files: 1
> README: UNLreport-1.02/README
> META.yml: UNLreport-1.02/META.yml
> YAML-Parser: YAML::XS 0.32
> META-driven index: no
> Timestamp of file: Wed Mar 2 04:26:29 2011 UTC
> Time of this run: Wed Mar 2 04:28:04 2011 UTC
>
> Status of this distro: OK
> =========================
>
> The following packages (grouped by status) have been found in the distro:
>
> Status: Successfully indexed
> ============================
>
> module: UNLreport
> version: 1.02
> in file: UNLreport-1.02/lib/UNLreport.pm
> status: indexed
>
> module: UNLreport::Line
> version: 1.02
> in file: UNLreport-1.02/lib/UNLreport.pm
> status: indexed
>
> module: UNLreport::_util
> version: 1.02
> in file: UNLreport-1.02/lib/UNLreport.pm
> status: indexed
>
> __END__
>
>
