summary
- security fixes
- indepence of /usr/bin/perl
- improved UNICODE support
- improved thread support
- misc. "minor" syntactical sugar (package Foo VER, __SUB__,
My €.1 about relying on stock /usr/bin/perl vs. latest and greatest:
It is true that vendor may choose to upgrade their perl in a way that is incompatible, and that this may hurt us.
But that will be true for anything installed on a box:
libc, libssl, openssh, bash.
The reason for incompatiblity may as well be due to some community/-ies changing policy/-ies
(like openssh vs. bash and the handling of .bash*).
And the incompatibility problem would certainly have hit us if we had choosen latest and greatest,
as 5.18.0 did move the given/when and ~~ into experimental mode
(and thus removing my best arguments...).
The only feasible way to handle this problem, is (at least in our case), automated testing of
our perl modules/scripts and all our other stuff, to ensure it works in the next new environment, whether it is new due to satellite server upgrades and/or a new version of latest and greatest.
-
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.
|
