in reply to Re^4: Namespace for local/internal modules?
in thread Namespace for local/internal modules?

Hmm, perlmodlib does suggest 

If developing modules for private internal or project specific use, that will never be released to the public, then you should ensure that their names will not clash with any future public module. You can do this either by using the reserved Local::* category or by using a category name that includes an underscore like Foo_Corp::*.

So that is as close to official as you can get

  • Comment on Re^5: Namespace for local/internal modules?

Replies are listed 'Best First'.
Re^6: Namespace for local/internal modules?
by tobyink (Canon) on May 24, 2012 at 12:22 UTC

    Indeed, and PAUSE's On the Naming of Modules document also implies that Local:: modules shouldn't be added to CPAN.

    perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
[reply]
[d/l]

In Section Seekers of Perl Wisdom