I think it’s not a bad idea. No features have been removed, only moved. It’s incumbent upon the developer to do a local library with tools like local::lib, perlbrew, and Carton. And that should be done anyway to control versioning, upgrades, bugs, and accidental regressions. The customer should never need to know anything about that level of the code and you can have a shiny new or version specific CGI and perl to your heart’s content. And you can always cut and paste the entire CGI.pm into your code if the other strategies are too much to to handle.
The refusal to embrace new deployment strategies is something that can enforce perception of Perl as antiquated. Move forward, you’ll find the tools afford much more than they cost.
-
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.
|
