After reading Traits: Composable Units of Behaviour I have the impression that, due to their statelessness, Traits (and Roles) are very much like Functors in some functional languages (SML).
So like map and anonymous subs bring some first-order functional programming into Perl, Roles bring higher order functional programming constructs allowing us to refactor the stateless logic into separate, more easily composable units.
Update: Thank you for all the answers! To explain what was the purpose of my post - I had this vague intuition (and since my studies 15 years ago I have not touched SML so it really just a remote glitter through the fog) - and I wanted to check how it matches other people understanding of Traits.
-
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.
|