comment on

<heresy>

As far as I can tell, mixins are yet another artifact of the mistaken belief that modelling The Real World^TM inevitably leads to better programming constructs.

The OO pioneers, struck by the apparent universality of abstraction and specialisation, and lured on by the taxonomical success of the biologists, had one key success, the creation of a powerful meme; the notion that object oriented methods must be pure in their conception, untainted by so called procedural thought.

This inevitably leads us to the current vogue; that to claim legitimacy, every new OO invention must have an appealing analogy in The Real World.

And mixins, by all accounts having their origin in an icecream store, and being as they are inherently an introduced novelty, are an indication of the extent to which the theorists are willing to embrace the farcical for the sake of conformance with the aforementioned meme of purity.

Mixins allow the would-be purist to program however they damn well please, all the while intoning the virtues of purity with a straight face.

</heresy>

In reply to Re: Implementing a Mixin Class by EdwardG
in thread Implementing a Mixin Class by Belgarion

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks