Your problem may come from the fact that the 'use' statements are evaluated at compile time, so the variable wasn't actually defined yet at the time the module was used. If that is the case, you can delay using the module either by wrapping it in an eval, putting the variable declaration in a BEGIN block, or doing require/import on the module yourself, instead of using use, or if the module is your own code (or you are willing to modify it), you could pass the path as part of the import...
# wrap the initial declaration in a begin block BEGIN { $softwarepath = "/usr/local/etc/software"; } use module; # or eval the use, so it happens at run time $softwarepath = "/usr/local/etc/software"; eval { use module; } # or do the require/import yourself $softwarepath = "/usr/local/etc/software"; require module; module->import(); # or modify the module to accept the path as an option use module path => "/usr/local/etc/software";
| We're not surrounded, we're in a target-rich environment! |
|---|
In reply to Re: Module and software path
by jasonk
in thread Module and software path
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |