A quick scan of them indicates that none of them will help me avoid either hard-coding config file paths into my modules, or needing to pass config hashes/objects into my modules so they know what's in the config file as well as my program.
Time to put my code where my mouth is and attempt what I suggest above.... should be interesting.
In reply to Re: Program configuration in the OOP world
by Tardis
in thread Program configuration in the OOP world
by Tardis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |