I like having a contract so I'd mix the method in through the magic of multiple inheritance.
package Base; sub new { bless \my($scalar), shift } package Optional; use Carp qw(croak); sub optional_method { croak q{You said you would implement optional_method and didn't!}; } package A; use base qw(Base); # No optional_method. package B; use base qw(Base Optional); # Must implement optional_method. sub optional_method { 'Woot!' }
You get ->can('optional_method') now but you also have your code croak if the contract isn't met. Or you can put shared code in the super Optional::optional_method. Your choice.

In reply to Re: OO design: abstract class or can()? by shanna
in thread OO design: abstract class or can()? by perrin

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.