Re^5: Configuration files

Are you the only Perl guy there? Then tell them they have the option of trusting you to write an extra bug-free module in time they hadn't budgeted for, or trust you to review some options from CPAN. Factoring out, they don't have the option of not trusting you :)

If you have other Perl people there, you can get them involved. With any luck they will be on the side of code reuse. Speaking of which, of course using a module helps *against* duplication!

You mentioned the perl installation several times. Keep in mind that *you do not have to change it*. Just as your main script *will* be copied over to n machines, so can the modules you need.

Comment on Re^5: Configuration files

Replies are listed 'Best First'.
Re^6: Configuration files by szabgab (Priest) on Jan 02, 2005 at 07:26 UTC
One of the solutions I saw often in similar situations is that the developer takes a real CPAN module, renames it (eg. turn YAML in to MyNameSpace::YAML) and that's it. I don't really like this solution and I am glad so far I did not have to do this, but this might help. This might also give you the opportunity - or the need - to actually read the source code of the module.	[reply]