Re: Proc#curry doesn't work on func which produces func

On Sunday 02 March 2008, Yusuke ENDOH wrote:
> By the way, I'm curious to know what purpose do people use
> Proc#curry for.

I know you know what currying is for; I'm just throwing some thoughts out=20
there.  It sounds as if you're looking for practical examples for=20
documentation.

A common use for me in FP has been extensible, custom printers.  For exampl=
e,

  logger =3D proc { |level, exception, source, message|
    if level_of( level ) >=3D LogLevel::current_level
      case level
        when :debug
          STDERR.puts "DEBUG [#{source}]: #{message}"
        when :error
          STDERR.puts "ERROR [#{source}]: #{message}"
          STDERR.puts exception.backtrace
        when :info
          STDERR.puts message
      end
  }
  @debug =3D logger.curry.call(:debug).call(nil)
  @error =3D logger.curry.call(:error)
  @info =3D logger.curry.call(:info).call(nil).call(nil)
  ...
 =20
  def some_method()
    ...
    @debug.call( "some_method", "Enter" )
    ...
    begin
      ...
    rescue
      @error.call( "some_method", !$, "It didn't work" )
    end
    ...
  end

Another very common use for currying is for pre-creating commonly used=20
functions that are simple compositions of other functions such as #map and=
=20
#inject.  Even in FP, the choice between using currying and using argument=
=20
tuples is largely one of which is going to be more convenient for the commo=
n=20
use of the function -- although there's an belief that, commonly, currying =
is=20
a better choice.  The logger example above could also be written:

  def logger( level, exception, source, message )
    ...
  end
  def debug( source, message )
    logger( :debug, nil, source, message )
  end

and so on.

=2D-=20
### SER  =20
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Haskell|Aikido|Iaido
### http://www.ser1.net, http://www.ser1.net/Security/ser_public.gpg
### Jabber: [e-mail] (OTR enabled)