Another point to consider is the extra pain that you might have to deal with when you upgrade support to a new platform. I just finished upgrading our large and complex Perl-based internal production system to run under a newer version of Linux which comes with a newer Perl and other newer library versions. We use a large number of CPAN modules, and there were three CPAN suites that had to be 'fixed'. BerkeleyDB had to be recompiled to match the older libdb we use for our binaries (couldn't use the vanilla libdb that came with the new version of Linux). IO::All and IPC::Run started producing warnings due to being older versions. I ended up installing the latest version of IPC::Run and that worked fine -- luckily the interface hadn't changed in a way that broke our code that uses it. The issue with IO::All turned out to be a bug(ish) that didn't produce warnings under older versions of perl, but does in the version we upgraded too. Since that was actually a bug, even against the older version of perl (which we also still need to support), I elected to fix the bug in place, which means that I didn't have to upgrade IO::All and risk having to update our code to adapt to any changes in a newer IO::All.

---

---

• 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.