Fair enough. It's not the case that currying is
equivalent to making a closure, though (currying is more
specific), but that's a minor point. The idea here is to
describe a way to avoid the parameter-handling that comes
with general-purpose functions, with as little lookup fuss
More generally, I'm turning into a functional-programming
evangelist, and since Perl makes it easy to use a lot of my
favourite techniques I'm writing about them here. Go up a
meta-level from my OP, and what I'm talking about is
building functions on an ad-hoc basis (compare to the static
"functions are global named objects and part of the design
document" world of straight procedural programming).
Whether you use literal subs or build higher
order functions to do it is less important than being
aware of the possibility.
Found a typo in this node? /msg me
% man 3 strfry
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||