I'm not going to comment on the name - I'm lousy with names :-) But I have to wonder about your motivation for writing this module - what's the purpose?
If a module is completely OO, you should be able to write the long name only once - when you call new() (or if you call new() several times, save the long name in a variable, as Gaal suggested). Afterwards, all the data and methods should be accesible using $object->method(), for example. Isn't that what OO is all about?
There was a discussion about this a while ago which started with a question I sent to the Israe.pm mailing list: http://perl.org.il/pipermail/perl/2004-December/006493.html
From what was said, I'm pretty convinced that you don't need a module such as the one you've written for OO modules. Am I wrong?
In reply to Re: Module Naming Dilemma
by SolidState
in thread Module Naming Dilemma
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |