Here's a little something I toss into packages that should be subclassed. I do something similar for "virtual" functions, too. -v
sub new { my $this = shift; my $class = ref($this) || $this; # This part prevents a user from creating an # instance of the package, but still permits # subclasses to call the parent's new(). my (undef, $filename, $line) = caller; $filename =~ s/^.*\///; die "Abstract class $class must " . "be subclassed at $filename " . "line $line.\n" if $class =~ /^Processor$/; bless $self, $class; return $self;

The subclassed code's new looks like this:

sub new { my $this = shift; my $class = ref($this) || $this; my $self = $this->SUPER::new(@_); bless $self, $class; return $self; }

In reply to Abstract Packages by Velaki

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.