Your module really is aliasing a namespace, yes? Mine just creates a subroutine that returns the package name and inserts it into the calling namespace (after doing some stuff to handle loading and importing.)

The important thing here is that the module name be very short to actually make it worthwhile to use. It's also been pointed out that this makes it easier to use a module that's merely been renamed.

Well, in answer to your question... I assume you're aware of the general restrictions/caveats on both top-level namespaces and lower-case namespaces. You should discuss your naming idea on comp.lang.perl.modules, and then on modules@perl.org which is where the PAUSE police lurk. I don't know who has the authority to issue a pragmatic module name; probably p5p or the pumpking.

Wouldn't it be simpler for
use class 'My::Company::Namespace::Customer';
to do the import and just:
@Customer::ISA = 'My::Company::Namespace::Customer';

On second thought, I think I prefer your way. Less side-effects that I can see.

I hope that you've documented (and possibly checked!) that your aliases can't contain things like :: in them.

If I didn't know how it was implemented, I could easily see myself being bitten by that.

(Note: I happen to agree with Perrin's response in your diary. I happen to dislike the idea and wouldn't use it. But then again, I don't have to.)

I don't understand. Why can't they have "::" in them? This works:

use aka "Really::Long::Module::Name", as => "R::Name";
my $foo = R::Name->some_class_method;
[download]

However, messing with someone else's namespace is a really bad idea and it is documented that the programmer shouldn't do that.

Cheers,
Ovid

New address of my CGI Course.