Modules, and namespace.
I make everything more difficult than it should be. This is something that a lot of tech heads do, and well, this is one of those things.
Without "registering" a module name, is there a 'Reserved' module space where a future module will not clobber something?
Is that even necessary, or am I being an Idiot? I've mentioned before that I'm from the land of C, and in C a module is basically a single file or a library. So, basically - a Module is anologous to a C library... (right?)
Of course, C, has explicit links and whole slew of of other ways to get around name clobbering (although, even there, it can create problems).
Worse, every time I start searching for information about making modules, everything is about making a module for CPAN... except what I'm doing is recurring database calls, that are specific to my environment.. DBD is great, and generic enough.
I'm smart enough to know that CPAN doesn't need another something::Simple
Where was I, oh yeah, Clobbering.
So I know I want to stop copying the same 10 functions between each of my web-programs, but I want to give it a module name that can't be clobbered later (we transition Linux dists often).
How does one go about this? Is there a way to set an Explicit load path for a wanted/required module? Does the naming to Module name convention have to follow the CPAN (Group=Directory)::(Module=filename.PM) mode?
So, I'm willing to read, is there some link you can point me to?