> It is to help the user develop a consistent and accurate configuration file.
Hmm ... I'm not sure I'd use a Modulino for this.
Something like
perl -mMODULE=foo
will use Module and call Module->import("foo") and you are free to let the importer do whatever you want, and you can have a variety of functions you can call.
see perlrun -[mM][-]module=arg... for details.
Of course calling a Modulino perl path/MODULE.pm foo can also validate the command-line options like foo here, but in this case your client needs to know the path to the installation.
|