in reply to Re: Module Naming Dilemma
in thread Module Naming Dilemma

Can you suggest a better name? I need something short and sweet. As for "sort of alters compile time behavior", it doesn't really, but it has the appearance of doing so. Thus, a pragma named "class" seemed reasonable. The name bothers me, but I honestly can't think of a serious objection to it. "aliased" might also be good:

use aliased "Some::Obnoxiously::Long::Name::For::A::Customer";
my $cust = Customer->new;

[download]

Cheers,
Ovid

New address of my CGI Course.

Replies are listed 'Best First'.
Re^3: Module Naming Dilemma
by PodMaster (Abbot) on Jan 04, 2005 at 22:35 UTC
    How about namespace::not? namespace::lite? oo::a? Now that you've divulged how it works, maybe you can contact the author of namespace and add an option for it to work like your implementation? or just go with namespace::lite?

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]

      Unlike namespace, I'm not trying to mimic C++ behavior. However, I can understand the similarity. However, just extending that namespace makes my module name long(er) again. Much of the point of this module is to simplify things. When I have to type more characters in my module name than the module who's name I'm trying to shorted, it kinda misses the point.

      Cheers,
      Ovid

      New address of my CGI Course.

[reply]

In Section Seekers of Perl Wisdom