Interesting.So you change $PATH and then run your "other" Perl. Will the $PATH automagically reset once your "other Perl" script starts or finishes? What if meanwhile some other (automatic) script wants to start Perl?
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply]
[d/l]
[select] |
Hi CountZero Um, $PATH is a variable, unless you write it down it only affects the current shell instance (works same for windows and %PATH%/cmd.exe )
Child processes get a copy of parents $PATH/%ENV
"automatic" scripts aren't spawned from existing shell instances... they often aren't spawned with %ENV initialized from .profile at all ( sourcing a shell script/.profile and importing into %ENV )
| [reply] |
Thank you! That made it clear. I'm probably still too much rooted in the old MSDOS-world where the shell was really the only thing you had and everything was affected by it.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] |