I'm using it regularly to run various tests when developing a module.

Like this I can always hit F5 in my editor, no matter in which file of a project I am.

And the current test-procedure is on top of my module in an

unless (caller()) { BLOCK }

Like this I don't need to always change a different make file to test the function I'm currently changing.

Thanks! I shall keep that in mind. The purpose of this validate() program is not to test my module. It is to help the user develop a consistent and accurate configuration file. Over the last 5 years of development, the syntax of this config file has become more complex. It winds up being possible to configure things that my SW doesn't consider an error, but nevertheless will could surprise the user. This is to make sure "that you've told the program to do what you want". So it spews out all sorts of explanations intended for a human to read. Updating this config file is serious business and is only typically done once per year.

> 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.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}