So that's what runtime polymorphism might be good for. In this particular case, I like it better than the classic subclassing approach.

So your point is that you don't like polymorphism as provided by standard OO (at least in this case), and therefore decide to re-implement it manually?

Somehow that fails to convince me, and painfully reminds of attempts seen here at perlmonks to re-implement pack or unpack, CGI::param(), various core modules and other stuff.

I like the Haskell's approach of pattern matching against signatures: 

divides x 2 = $(special cased implementation)
divides x y = $(general-cased implementation)

[download]

It seems that to me that replacing object methods at runtime is a rather limited solution to this problem, because it works only for methods (not for subs, although they'd profit from the same mechanism), and more importantly, it only works for special-casing on the object. As soon as you want to special-case on the parameter (say, you know it's a prime, and thus always return false).

I don't know what's the best perlish approach is, but re-implementing an existing technique and thereby retaining the limitations doesn't exactly seem right.

In reply to Re: Motivation for replacing object methods at runtime by moritz
in thread Motivation for replacing object methods at runtime by Narveson

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.