I think a good place for me to put my future modules on CPAN is into the
Marquis:: namespace--which currently does not exist.
What do the rest of you think of this idea?
--
paduille.4060.mumia.w@earthlink.net
>>>>> "MW(n" == Mumia W (reading news)
MW(n> I think a good place for me to put my future modules on CPAN is into
MW(n> the Marquis:: namespace--which currently does not exist.
MW(n> What do the rest of you think of this idea?
if this is a personal set of random modules, i would say no. top level
namespaces should be used for larger namespaces. why do you want this
name? what kind of modules and are they related? does marquis have a
technical connection here or is it just a name you like?
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
On 12/05/2006 10:41 PM, Uri Guttman wrote:
>>>>>> "MW(n" == Mumia W (reading news)
>
> MW(n> I think a good place for me to put my future modules on CPAN is into
> MW(n> the Marquis:: namespace--which currently does not exist.
>
> MW(n> What do the rest of you think of this idea?
>
> if this is a personal set of random modules, i would say no. top level
> namespaces should be used for larger namespaces. why do you want this
> name? what kind of modules and are they related? does marquis have a
> technical connection here or is it just a name you like?
>
> uri
>
It's just a name I like. Underneath Marquis:: would be a hierarchy of
namespaces for the modules I've written such as Marquis::Math and
Marquis::Sort.
I don't want to create more namespace pollution on CPAN, but I do want
to keep my module hierarchy separate from the others.
The first module I intend to submit is Marquis::Sort::KeyExtract :
> NAME
> Marquis::Sort::KeyExtract - Sort using a user-specified key extractor
>
> SYNOPSIS
> use Marquis::Sort::KeyExtract;
>
> my %months = (
> January => 1,
> February => 2,
> March => 3,
> April => 4,
> May => 5,
> );
>
> my @array = (
> 'District conferences will happen in =February (20-21)',
> 'Coat sales are in =January.',
> 'In =May, we meet with the directors.',
> '=March will see new matrices form.',
> 'Taxes are to be paid in =April.',
> );
>
> my $sorted = sort_keys {
> code => sub { s/=(\w+)/$1/ && $months{$1} },
> }, \@array;
>
> print "$_\n" for (@$sorted);
> [...]
http://home.earthlink.net/~mumia.w.18.spam/perl/KeyExtract.p od
http://home.earthlink.net/~mumia.w.18.spam/perl/KeyExtract.p m
--
paduille.4060.mumia.w@earthlink.net
>>>>> "MW(n" == Mumia W (reading news)
MW(n> On 12/05/2006 10:41 PM, Uri Guttman wrote:
>>>>>>> "MW(n" == Mumia W (reading news)
>> MW(n> I think a good place for me to put my future modules on CPAN
>> is into
>> MW(n> the Marquis:: namespace--which currently does not exist.
>> MW(n> What do the rest of you think of this idea?
>> if this is a personal set of random modules, i would say no. top
>> level
>> namespaces should be used for larger namespaces. why do you want this
>> name? what kind of modules and are they related? does marquis have a
>> technical connection here or is it just a name you like?
>> uri
>>
MW(n> It's just a name I like. Underneath Marquis:: would be a hierarchy of
MW(n> namespaces for the modules I've written such as Marquis::Math and
MW(n> Marquis::Sort.
MW(n> I don't want to create more namespace pollution on CPAN, but I do want
MW(n> to keep my module hierarchy separate from the others.
that is not a good reason to get a top level namespace.
MW(n> The first module I intend to submit is Marquis::Sort::KeyExtract :
what does the Marquis prefix do? the rest is fine as it is.
you can always upload modules to your cpan home dir. email the modules
list to discuss namespaces but they will likely agree with me that there
is no need for this top level name. just put sort modules under Sort::,
etc. your home dir will list all of your modules so you can see them all
that way.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
On 12/06/2006 09:37 AM, Uri Guttman wrote:
> [...]
> you can always upload modules to your cpan home dir. email the modules
> list to discuss namespaces but they will likely agree with me that there
> is no need for this top level name. just put sort modules under Sort::,
> etc. your home dir will list all of your modules so you can see them all
> that way.
>
> uri
>
I started thinking about putting my module into the Sort::KeyExtract
namespace, and I got curious about what other Sort::Key* modules were in
that area.
It seems that Salvador Fandiño has already written a Sort::Key which
seems pretty good.
Actually, it's frighteningly good. I'll delay posting my module for
right now.
http://search.cpan.org/dist/Sort-Key/lib/Sort/Key.pm
versus
http://home.earthlink.net/~mumia.w.18.spam/perl/KeyExtract.p od
:-[
--
paduille.4060.mumia.w@earthlink.net
Mumia W. (reading news) wrote:
> On 12/05/2006 10:41 PM, Uri Guttman wrote:
>
>>>>>>> "MW(n" == Mumia W (reading news)
>>>>>>>
>>
>>
>> MW(n> I think a good place for me to put my future modules on CPAN
>> is into
>> MW(n> the Marquis:: namespace--which currently does not exist.
>>
>> MW(n> What do the rest of you think of this idea?
>>
>> if this is a personal set of random modules, i would say no. top level
>> namespaces should be used for larger namespaces. why do you want this
>> name? what kind of modules and are they related? does marquis have a
>> technical connection here or is it just a name you like?
>>
>> uri
>>
>
> It's just a name I like. Underneath Marquis:: would be a hierarchy of
> namespaces for the modules I've written such as Marquis::Math and
> Marquis::Sort.
>
> I don't want to create more namespace pollution on CPAN, but I do want
> to keep my module hierarchy separate from the others.
>
This sounds like the way Java does things. Or at least the way I
understand Java to do things.
But Perl namespaces have always been more-or-less functional, and you're
making it harder for others to browse for your modules. To the best of
my knowledge there are no personal namespaces on CPAN, and though the
namespace czars seem to be more lenient these days, I for one would
think the spawning of a bunch of personal namespaces would just make the
naming situation worse.
As was pointed out in an adjacent response, there's no trouble finding
modules by author. Assuming your PAUSE account is 'mumia', your modules
would be under http://search.cpan.org/~mumia/
If you are determined to pursue this, maybe propose top-level namespace
Personal::, and then make your stuff Personal::Marquis::. The Acme::
namespace seems to me to be a precedent, in that the only uniting
functional thread that I can discern is off-the-wall-ness (if you will
pardon the invention of a word).
Tom Wyant