Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

belg4mit (967)

  (email not shown publicly)

Journal of belg4mit (967)

Wednesday October 14, 2009
02:14 PM

Namespace pollution

[ #39756 ]

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.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • So everyone should make their modules in this way that you love? ;)
    • 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.

      Were that I say, pancakes?
  • 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. :)

    • 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.

      Were that I say, pancakes?