Kai Jendrian wrote:
> This sounds like an iteresting option which adds some additional > overhead to the solution I had figured with the shell script but it > gets rid of maintaining a second file with code. Good point! Overhead should be the same: A shell script is just one type of process starting the Perl program; versus a Perl process restarting itself. If you force the user to set the environment variables, you can start directly without any front end environment setter and then you save time. That's bad practice IMO -- we don't need to set environment variables to run commands that come with the system. It's okay to allow environment variables to control things and provide defaults. That's different than *requiring* them to be set. One other step I often take with Perl is to write a separate Env package associated with each package that needs default settings. That way, a Perl user can use @INC to pick up their own Perl package instead of the default I install. -- Steve Sapovits [EMAIL PROTECTED]
