David Abrahams wrote:
Brian Braatz wrote:
What is cool is THIS PAGE:
What stood out about it was THIS ONE PAGE would have saved me many many hours had it been in the original Lambda docs. Because it describes for me, how to "think" about the currying. >
Unfortunately this page confuses currying with partial function application as I explain here:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52549
and also in this thread: http://tinyurl.com/4tgez
I believe I patterned this after FC++: http://www.cc.gatech.edu/~yannis/fc++/currying.html http://www.cc.gatech.edu/~yannis/fc++/currying-tutorial.txt Are you saying that Brian and Yannis also got it wrong? ''' "Currying" basically refers to the ability to call a function on some subset of its arguments; such a function can be referred to as "curryable". The result of calling a function with only some of its arguments is a new function, which expects the rest of the arguments. ''' In a link that you provided: http://wombat.doc.ic.ac.uk/foldoc/foldoc.cgi?curried+function it is defined as: A function of N arguments that is considered as a function of one argument which returns another function of N-1 arguments. IMHO, sticking strictly to this definition is pedantic. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net