|No such thing as a small change|
How to have multiple Perls under Windowsby adamsj (Hermit)
|on Aug 14, 2001 at 07:41 UTC||Need Help??|
adamsj has asked for the
wisdom of the Perl Monks concerning the following question:
My travails with IO::Socket under WinME (and I've now gotten the same problem with Win2000) are documented elsewhere and a possible reason for it has been given. I'm going to fire up my "laptop" (which needs a monitor and a keyboard to work...sigh) and try putting the client and the server on separate machines and see if that doesn't fix my problem--but I'm thinking there's yet more to do.
It occurred to me that this odd behavior might be an artifact of the ActiveState implementation in particular, rather than just how things were under Windows, so I decided I'd put a different Perl on my machine and see what happens.
Then, the question arose in my mind, "What if I had two different versions of Perl--say, ActiveState and IndigoPerl--running on the same machine, and started the client with one and the server with the other--what then?"
This led me to the $64,000 dollar question--"How badly am I going to screw up my machine by putting (or, more likely, trying to put) multiple Perls on it? I know how to do this on UNIX, but on Windows...hmm."
Being foolhardy, I went ahead and tried putting IndigoPerl on, and it's not cooperating. I suppose trying SiePerl is next, but I wonder--does anyone else have experience, frightening or otherwise, with this silly idea?
They laughed at Joan of Arc, but she went right ahead and built it. --Gracie Allen