CGI.pm is included with the Perl core distribution, so you can reasonably expect your code to run pretty much anywhere (barring other non-portable things of course). This may or may not be an advantage for you.

I agree with you that clear separation of functionality is a good thing, and that CGI.pm tries to do everything. Even the author of CGI.pm admits that it should be discarded in favour of better-designed modules.

As with anything, I think it depends on what you want to do. I'm only familiar with CGI.pm, and know nothing (yet :-) about the other CGI modules you mention. If the separate modules (CGI::Base, etc.) have the functionality you need, I'd say go for it, and don't use CGI.pm.

--
All that is gold does not glitter...

In reply to Re: CGI.pm vs. CGI modules by Aragorn
in thread CGI.pm vs. CGI modules by rruiz

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.