|
![](/i/fill.gif) |
Orchid XP v8 <voi### [at] dev null> wrote:
> Currying, not so much. (Other than that it's something people often do,
> so they use the technical term for it. Rather like inheritance gets
> mentioned a lot in OO languages, even though it's just a short cut for
> duplicating code.)
The difference, to me, is that I understand what inheritance is and why
it's useful. I can't say the same about currying or monads.
Btw, in the articles mentioned in the original post the example is
given of making an int "nullable" via a monad (or something along those
lines). I can't comprehend what this has to do with I/O (or, more precisely,
I can't understand what this kind-of "inheritance", which is what it looks
like to me, has to do with I/O), as the I/O monad seems to be one of the
main concepts of haskell.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |