Namespace pollution

belg4mit on 2009-10-14T19:14:00

Arggh! Enough with the bloody vanity pseudo-pragmas and other modules to enable some combination of features-you-love-and-so-should-everyone-else sprinkled all-over CPAN. Create a bloody ToolSet or ToolSet::Bundle. That's what they're for, and it keeps all of that crud^Wbeauty collected together for ready comparison and retrieval.


preference

slanning on 2009-10-14T22:24:28

So everyone should make their modules in this way that you love? ;)

Re:preference

belg4mit on 2009-10-14T22:51:38

Actually, I gave two ways :-P

And I suppose they could put something into that namespace which is not implemented with either of them. While the name might not then be hierarchically correct i.e; implied inheritance is missing; at would be thematically correct.

Regardless, the "prohibition" against non-pragmatic lowercase module names is not mine.

use zealotry 'AUTHOR';

Alias on 2009-10-15T05:21:48

At work, we've been discussing the idea that we could push all these zealots and their pragma congloberations into one namespace...

Some kind of use Zealotry::CHROMATIC, use Zealotry::MLEHMAN, etc would be interesting I think. :)

Re:use zealotry 'AUTHOR';

belg4mit on 2009-10-15T16:53:04

Heh-heh. Sounds good. Actually Zealotry::MONS is the straw that broke the camel's back as it were, but the foundation was laid by others.