Re^2: Multiple instances of Perl

You should not run different versions of perl.

Sure you should if you are advanced beyond beginner level. I would envision a common setup being a regular Perl in /usr/bin and a C debugging-enabled version in /usr/local/bin. Someone has to be able to debug scripts, to a lowlevel, and it's a waste to have a separate computer for a debugging version.

I'm not really a human, but I play one on earth. Cogito ergo sum a bum

Comment on Re^2: Multiple instances of Perl

Replies are listed 'Best First'.
Re^3: Multiple instances of Perl by Joost (Canon) on May 14, 2008 at 21:31 UTC
This is exactly what I do. I generally have whatever is the latest stable perl w/debugging/threads/whatever I want in /usr/local/bin and leave /usr/bin/perl to the system packages. That way I can experiment with different CPAN packages and my own code while still having a stable system. I would really not recommend replacing /usr/bin/perl with your own versions on unix/linux - if you're unlucky, it can really mess up your system. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^3: Multiple instances of Perl by apl (Monsignor) on May 15, 2008 at 11:59 UTC
My employer (a brokerage) uses three machines per Production product: development, where it doesn't really matter what state the software or environment is in QA, where the latest stable environment / software is available for testing Production. Please keep in mind that some of us may be talking at cross-purposes. My software only runs under one version of Perl under Solaris, and is maintained solely for our use. If you were developing classes that needed to run under Perl 5.0, 5.8 and 5.10 on user-owned machines, I see the necessity of multiple Perl environments on one box.	[reply]