Thanks folks.
The script is most easily distributed (and installed) as a single file, that can be called as any standard (*nix) utility would be called, w/o additional command line arguments or forced interpreters (and I want to avoid a wrapper script). In one usage scenario, I do not control the calling context, so it must be callable as:
/path/to/script
and that's it.
In the second usage scenario, the script is used standalone, where I could distribute and require installing the modules. But because of the requirement above, I don't want to have two different running contexts, where some unforeseen problem creeps in due to my misunderstanding the process required to translate modules into a single, standalone script. (I just encountered such a problem this evening, where running the single-file version produced an error, but the module-based version did not.)
In reply to Re: Cat'ing perl modules into single file script
by Smitty
in thread Cat'ing perl modules into single file script
by Smitty
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |