Sriram on Currying in C# 2.0

Yes, generics certainly leads to clear and understandable code...

Does someone have an example of when "Currying" is useful?

Is it just me or are people seriously coming up with "common-sense/clear as day" terms and methodologies...

Wolm:

From Wikipedia: "The practical motivation for currying is that very often the functions you get by supplying some but not all of the arguments to a curried function are useful; for example, many languages have a function or operator similar to plus_one. Currying makes it easy to define these functions."

Lecture notes on currying: http://www.informatics.sussex.ac.uk/courses/funcprog/Handouts/lecture5.pdf

I'll leave it to you to actually look things up, if you're interested. Personally, I'm more gung-ho over LCG.

Yes -- I read the Wikipedia too, but I didn't find the lecture. Thanks for that.

But still. I'm looking for a useful example beyond "an easy way to define a function for the ++ operator".

Or in other words: How is currying going to help me in my everyday software development?

Within the span of 2 days, I get linked to by first Don Box and now, Rico Mariani. This has meant that...

Currying useful to create anonymous functions without writing lambdas.

imagine that we need to append 2 for each element of list l. In haskell it will be:

let f = \x -> add(x, 2) -- creating lambda
in map(f, l) -- applying it to list

with currying it looks like:

let f = add 2
in map f l

Evaluation of (add 2) returns function which accepts single argument and sums it with 2.