stvn, thanks for your comments. Let me address this one, in particular:
For instance, your technique would not work with OO, ...
Why not? For example, here I use currying to pre-bind a method to a particular object instance: 
    #!/usr/bin/perl

    package MyObj;

    use warnings;
    use strict;

    use AutoCurry ':all';

    sub new {
        my $self = shift;
        my $name = shift;
        bless [$name, { @_ }], $self;
    }

    sub speak_keyvals {
        my ($name, $hash) = @{shift()};
        print "$name sez: @{[ @$hash{@_} ]}", $/;
    }

    my $foo = new MyObj( "foo", a => "alpha", b => "beta" );
    $foo->speak_keyvals( "a" );
    # foo sez: alpha


    # for the next line, recall that $o->f(...) === f($o, ...)

    my $foo_speaker = $foo->speak_keyvals_c();  # binds to $foo

    $foo_speaker->("b");
    # foo sez: beta

    $foo_speaker->(@$_) for ["a"], ["b"], ["a", "b"];
    # foo sez: alpha
    # foo sez: beta
    # foo sez: alpha beta

[download]
Also, regarding this:
I also take issue with the idea that there is something wrong with design-time decisions to support currying.
To clarify, I didn't say that there was anything wrong with design-time consideration of currying. What I said was that it was a bad idea to require design-time considerations in order to make a currying scheme work. With such a requirement, the vast existing wealth of CPAN is placed beyond the reach of currying.

I don't want my ability to use currying to be dependent upon somebody else having designed it into the code I'm using. I want to be able to take old, existing code and curry it, as is.

Cheers,
Tom

Tom Moertel : Blog / Talks / CPAN / LectroTest / PXSL / Coffee / Movie Rating Decoder

In reply to Re^6: Near-free function currying in Perl by tmoertel
in thread Near-free function currying in Perl by tmoertel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.