I agree having to use print with a newline instead of say is not a good reason to upgrade ...
yet I'm struggling to understand your seemingly blase attitude towards Security.
(Oh, and I strongly agree that chromatic's Perl (and agile dev) books are awesome! ;-).
I suspect you come from a different (smaller?) commercial environment than me. Do you have Security auditors?
We do, they use tools (luckily mostly Windows-only for now) and they have the ear of upper management.
If you're using a version of Perl open to security exploits (see perlsec ... DoS attacks based on Perl hash algorithmic complexity
spring to mind) or any product (including Perl) that is out of official support, they'd be all over you like hair on soap.
They don't have the time to understand all the nuances of every product running on every computer so they tend to heavily rely on tools
and enforce blanket rules, such as "you are not allowed to use a product that is out of support" or
"you must regularly check for exploits and patch your software promptly".
-
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.
|
