Greetings, fellow monks.
I am currently working on a project that, like every other project, needs a config file.
I've read about a few options for handling the need for config files - from building a parse for name=value pairs to just having a config.pm that has all my configuration stuff inside it, to using Config::foo, and so on.
Long story short, I'm no longer certain which format to use(or how to accomplish it).
I need the config file to be able to contain Perl code, which means I can't use the first method I mentioned.
However, I'd also like it to insinuate its data into a global %config hash - so that I can refer to it from anywhere within my collection of scripts by simple doing this:
use config; print $config{foo};
Does anyone have any recommendations on how to implement this in Perl, or a module I could use that would help me accomplish this?
Thanks,
Spidy
In reply to Config file recommendations? by Spidy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |