it's always felt backwards to me that the burden is on users of new releases to enable new, non-experimental things to prevent users who don't update their Perl from having to update their code.
Philosophically I would agree. The move to v7 isn't a philosophical one, however; it's a practical one. From a practical standpoint I really can't see how having one line of boilerplate of maybe 10 characters or so can really be classed as a burden. To follow your path I would only need to add it once to my stock script/module template and we're done. And given that this replaces the current, longer boilerplate it's even better. Your new code is shorter, slicker and has all the new features and those still having to support 5.6.0 need do nothing. In the immortal words of the late, great Errol Brown, "Everyone's a winner, baby!".
-
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.
|