But I can subclass already by doing:

package src::bo::Rubber;

use strict;
use warnings;

use Carp;

use src::bo::Duck;
use base qw/src::bo::Duck/;

use src::bo::CannotFly;
use src::bo::CanSqeek;

sub new {
    my $class   = shift;
    my $extends = $class->SUPER::new(@_);
    $extends->setFlyBehaviour( src::bo::CannotFly->new() );
    $extends->setQuackBehaviour( src::bo::CanSqeek->new() );
    bless( $extends, $class );
    return $extends;
}

[download]

In the case of this strategy pattern I don't think I would gain much. Maybe you know of other cases?

--
if ( 1 ) { $postman->ring() for (1..2); }

In reply to Re^2: A quicker way to have protected and private fields? by gargle
in thread A quicker way to have protected and private fields? by gargle

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.