what is built in to perl dist these days that is meant to take the place of CGI.pm?
Short answer: nothing. The philosophy seems to be that since CGI.pm is no longer the de-facto standard for such tasks and has some other drawbacks that it shouldn't be in core rather than there should be something to replace it. A quick search here will show you many discussions about this over the past couple of years so you can look there for the rationale. (Update: Here's one such discussion posted only last month, for example)
My preference these days is for CGI::Lite. It has no non-core dependencies, is lighter (!) and faster than CGI.pm and doesn't require gcc to install because it is pure perl. There are plenty of other CGI implementations out there and there are also a bunch of framework-in-a-box options if you fancy that: Mojolicious, Dancer2, even Catalyst for the brave.
Take some for a spin and see how you get on with them. Folks here will be able to give you ideas but it's a very personal decision which to use depending on whether you prefer speed, resilience, security, flexibility, etc.
-
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.
|