Perhaps I should just stick to print statements and drive it myself as I don't necessarily always have access to compile install other modules so I am not able to use other than what's available.

No, "print statements" are what the complainers about CGI.pm are talking about

If you're making "cgis" the CGI.pm module is the absolute bare minimum,

it provides you with header function for generating the headers you want, cookies for cookies, and param function for getting the data

None of the alternatives to CGI.pm for speaking CGI are as good as CGI.pm

What you want to avoid is just print statements everywhere

If you read CGI::Alternatives you can see what the people complaining about CGI.pm being backwards are really complaining about, and its not header/param, its the no organization , no subroutines/reuse, one shot style ... RAW

For a bare minimum of contrast see cgi101 , sub RootPage, sub RootTemplate , ..., unclunky cgi, ...

Contrast increases only a little bit with with CGI::Application .... If you're using CGI.pm and following CGI to mod_perl Porting. mod_perl Coding guidelines you're 98% modern , only 2% away from using any "modern frameworks" which have a response object

In reply to Re^3: using HTTP::Response directly to speak CGI by Anonymous Monk
in thread using HTTP::Response directly by Habs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.