perrin's class factory suggestion sounds good, as long as the behavior changes globally. For per-object changes something like
Class::MethodMaker's method proxying may be more appropriate. Basically you setup a normal composition relationship (StoneGatherer has a Gatherer) but the particular Gatherer object is held in an attribute. Then you define the list of methods that should be proxied to the Gatherer that's actually in use.
This is something like the system used by Krang to manage the relationship between elements and element classes. Each element is assigned to an element class at runtime and the object behaves as though the element class is its base class via proxying. For example, this code:
$element->publish();
Is really:
$element->class->publish(element => $element);
-sam
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.