You can point to a network Perl install with really no problems. I used to do that. Now I use ActiveState's PerlApp, though, to create a packaged .exe file that can be distributed easily without regard to who has Perl installed and what modules they have.
-----Original Message----- From: zanardi2k2 [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 04, 2002 9:45 AM To: [EMAIL PROTECTED] Subject: Perl distribution and use I'm new to Perl but it seems to fit for my network administrative tools. Right now, we are using a mix of dos batch files, visual basic, c, relay and many other languages to create the tools we need. One of my favourites Perl features is the fact that since it is an interpreted language, we can change anything very quickly; but we are not limited in the possibiliy. I quickly learned that you can do *many* things with Perl. Now, my question: - if i want to run my scripts on different machines over the network (Windows), should i install a Perl interpreter on each machine or can i point to a network perl executable without troubles? TIA -- Zanardi2k2 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
