The big problem with monkey patching is that no two modules can safely monkey-patch the same third module. Recently there was a rather drastic example in the Ruby community when two large libraries or frameworks added incompatible json methods to Class (or was it Object? dunno...), and that meant you couldn't use these two libraries in the same process.

Your approach doesn't solve this problem. And it can't, because it's not reasonably solvable.

I might add that source filters suffer from the same problem as monkey patching: you can't combine two source filters fiddling with the same piece of syntax.

Perl 6 - second systems done right

In reply to Re: Safer monkey-patching by moritz
in thread Safer monkey-patching by tobyink

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.