The stupid question is the question not asked | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I had a useful program criticised because someone doesn't want to "install" Perl on the target machine.
Hey, if VB wants to drag around a multi-megabyte DLL, why not Perl programs? Besides making the files available on the file system, what is really necessary to run perl.exe on a Windows system? For a trivial script, it appears that nothing that's in the registry is actually used, and what it is looking for isn't present. So, I think it comes up with the @INC all by itself based on the exe's location. Is that correct, or is there some other hidden configuration somewhere? Is there anything else I should know about besides (1) seeing the directory tree and (2) making sure @INC points to it? —John In reply to Running Perl Programs without 'installing' Perl by John M. Dlugosz
|
|