Here I am again, in need of advice. Sometimes I think this
project will never end. I suspect that once you begin
writing a module it takes on a life of its own. Thanks for
all the help so far.
Are there any established module naming conventions? I have
a module that I hope will be an enhancement to
Term::ReadKey and it has two subs: which for
now I'm calling LoadKeyHash, and Keypressed.
I had originally wanted to name the module
Term::Keypressed but ran into a few error
messages that seem to indicate that it wasn't
happy with a module being named the same thing as an internal sub.
So I've renamed it Term::TermKeys which I
think is a more general description of the module (and am
happy with now).
Module Term::ReadKey (Readkey.pm) also has several
subs named ReadKey (the one actually used is determined
conditionally and defined via eval) but has several other subs
defined within it. Is it more common to name a module after a
principal sub, or should it be more descriptive of the
purpose/functionally of the module? Am I just splitting hairs here
or does any of this matter?
Thanks for any advice/opinions you can provide. I wouldn't be so
picky if it were just for my own personal use, but the goal is to
make this available for others to use (if it's deemed useful) and
possibly a tutorial on it's use as well.
@a=split??,'just lose the ego and get involved!';