Why put the data in .pm files? Can't it be controlled by data structures in some readable way, like JSON, YAML, or CSV? Does it need to include code? If parameters in the config files can control program flow in the module, I'd say stick to config files and not dynamic modules. An alternative to JSON, YAML, or CSV might be to look at any of the plethora of Config:: modules on CPAN.
update: that was a browser hick-up. Sorry. Just view the other answer.
In reply to Re: Best way to dynamically use a .pm?
by Tux
in thread Best way to dynamically use a .pm?
by TJPride
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |