Re: Module Naming Dilemma

What do you mean sort of alters compile-time behaviour?

My first reaction is also "No!" because so far it sounds similar to modules such as

and/or

use Module::Blah qw[ yada yada ];
use constant Boing => 'Module::Blah';
[download]

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.

Comment on Re: Module Naming Dilemma Download Code

Replies are listed 'Best First'.

Re^2: Module Naming Dilemma
by Ovid (Cardinal) on Jan 04, 2005 at 22:26 UTC

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.

[reply]
[d/l]

Re^3: Module Naming Dilemma

by PodMaster (Abbot) on Jan 04, 2005 at 22:35 UTC

[reply]

Re^4: Module Naming Dilemma

by Ovid (Cardinal) on Jan 04, 2005 at 22:57 UTC

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]


Come for the quick hacks, stay for the epiphanies.
	PerlMonks