Talk:Currying concept
The second paragraph of this article is gibberish. Actually, the whole article is poorly written and consists mostly of big unexplained blocks of Perl code. I would almost prefer to delete it than to try to salvage it. k.lee 05:12, 19 Sep 2003 (UTC)
Incomprehensible[edit]
I agree, the article really does not make much sense to me. Also, it's boldly copied from Perl Design Patterns, except that whoever copied it here in the first place missed the first lines, which are:
|
Problem Code is repeated and resists being refactored out. Solution Make the process of building the function or object you ultimately need and incremental process, requiring fixed or variable information at each state. |
Admittedly, the article still does not make much more sense, nor does the design pattern. Is this just constructor overloading?
See the article on currying though. It seems this is one of those things in functional programming that are really neat - but I can get by fine without it.
- I agree. This and the other articles pulled from "Perl Design Patterns" are very hard to follow. They should be rewritten. Tjdw 04:26, 1 Apr 2004 (UTC)