comment on

I dont see any reason to "upgrade" a perl install. Do a parallel install of as many different versions as you choose. So long as they are in totally different directory trees they will never know the others exist. Then write and deploy your code for the new versions and leave the old code alone except if you have a really good reason to decide that it should be ported to a later perl.

I think the biggest issue in this line of discussion is that everybody assumes that you must "upgrade" Perl. Its not an OS, you can quite happily have loads of different versions available at the same time.

---
$world=~s/war/peace/g

In reply to Re^2: Don't fear change by demerphq
in thread Why non-core CPAN modules can't be used in large corporate environments. by Moron

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks