I read through all of perlmod, and am familiar with the conventions. However, since this is a completely private module, I wanted to be able to use existing values to access the modules directly (although I've since implemented a hash using the values).
I stated before, that I've tried several different names for each of several .pm files (base was probably a bad example :) Because I'm using the hash, I can really name them anything I want to now. However, this opens up a new question:
Shouldn't my program have been able to
require baseif base is a preexisting module? (My feeling is that, because it's a core module, it can't be directly used or required.)
45 minutes later:I was able to find a different module (haven't played with the "base" one again), but I had to name it something different than what I had intended. (I had intended Nfs.pm, but that was never found, so I used "Nfs_module.pm", and it found that just fine). So I guess my question now becomes, why can't I use an arbitrary name for a perl module?
In reply to Re: Re: can't find my module?
by arootbeer
in thread can't find my module?
by arootbeer
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |