Subclassing (inheritance) should only be done to classes (modules) that were designed to be subclassed. CGI.pm was not really designed for that so I would strongly discourage doing that.

Besides, inheritance would be my last choice for incorporating features from another module into my module. Working with inheritance (at least implementation inheritance, which is really the only inheritance supported by Perl) is like working with big sheets of two-sided duct tape: Sure, you can stick things together really well, but it is just too easy to end up with too many things stuck too tightly together such that you can't work with anything anymore. (:

        - tye (but my friends call me "Tye")

In reply to (tye)Re: subclasssing vs using by tye
in thread subclasssing vs using by chorg

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.