The purpose of an abstract class is to constrain the implementor of its subclasses. This being perl, we don't try too hard to prevent circumvention of our constraints. So a very simple implementation of an abstract class is:

  package BaseClass;

  sub new {
    my ($class, @args) = @_;
    my $self = bless {}, $class;

    $self->init(@args);
    $self->check_interface__BaseClass;
    $self;
  }

  sub init { die "oops, this is the base class" }

  sub check_interface__BaseClass
  {
    my ($self) = @_;
    foreach my $method (qw[ foo bar baz ])
    {
      $self->can($method) or die "method $method not implemented";
    }
  }
[download]

With this simple approach, if your subclasses don't redefine "new" (they define the init method instead), then they get the interface checking. If they do redefine "new", then they can still check the interface by calling the check_interface method explicitly.

Sure, it has its limitations, but if you want a lightweight solution, this seems to fit the bill. --Dave

---

---

• 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.