Actually, I considered an "ini" or "cfg" file, but rejected it. I was wanting something more "standalone" in this case. First, it seemed a bit much for only 4 parms. Second, I didn't want to maintain a separate file. Third, I didn't want to parse an "ini" file, although there is likely a CPAN module around to do that. And I already use LWP::UserAgent and HTTP::Request::Common, so requiring another CPAN modules is not really a big deal. I really appreciate CPAN!
--As for the rest, it is mine.
Personal opinion: A cfg file is much easier to update/maintain then environment variables, and a command line is easier to use for 'variable' setups. For a case like this I would probably want to use a combined commandline/config file setup. Luckily, that only requires *one* CPAN module: AppConfig. It will handle both, in either order.
Daniel T. Staal
--------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---------------------------------------------------------------
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>