From ggrothendieck at gmail.com  Sat May 26 19:07:41 2012
From: ggrothendieck at gmail.com (Gabor Grothendieck)
Date: Sat, 26 May 2012 13:07:41 -0400
Subject: [Rd] Curry: proposed new functional programming, er, function.
In-Reply-To: <4FC1050D.3080306@gmail.com>
References: <7098abec0711011200va3851o811f60bb100616ce@mail.gmail.com>
	<BANLkTi=jud5hhis5y-veQKZHzSYYoPqnBw@mail.gmail.com>
	<79F23BA7BB084E4FA01A8B93904CD02CF669FAA4C9@WIGGUMVS.win.ad.jhu.edu>
	<4DC16917.5090206@gmail.com>
	<BANLkTikuy3OP8j5aymKuE_zmHtYLCkBZWg@mail.gmail.com>
	<79F23BA7BB084E4FA01A8B93904CD02CF669FAA4D7@WIGGUMVS.win.ad.jhu.edu>
	<BANLkTikvfsyZaW4wDB8sA-Z7G-rMQ+11Tg@mail.gmail.com>
	<BANLkTikGcviLYfFska4vkf5GpuCpmKTdJw@mail.gmail.com>
	<BANLkTik-1s+Af541ZkM+mDVkjRx94WM_4w@mail.gmail.com>
	<1337802805327-4631127.post@n4.nabble.com>
	<CABdHhvF1zJpDYXo3i7N30r5OQ0_Qj99_Rzpg-2oNRkdDNJFDfw@mail.gmail.com>
	<4FBFE810.5070405@gmail.com>
	<CABdHhvHzLj_BAjx+pMeP2YT9QQEV=_wVw8c3NqTBfp2XHLt6Eg@mail.gmail.com>
	<4FC1050D.3080306@gmail.com>
Message-ID: <CAP01uRkeawBJWgeMez8DYy5fOAOzQE2XE-=7vd=z26WybikRFA@mail.gmail.com>

On Sat, May 26, 2012 at 12:30 PM, Yike Lu <yikelu.home at gmail.com> wrote:
> On 5/25/12 5:23 PM, Hadley Wickham wrote:
>>
>> On Fri, May 25, 2012 at 3:14 PM, Yike Lu<yikelu.home at gmail.com> ?wrote:
>>>
>>> So here's the way I'm reading this:
>>>
>>> Original:
>>> curry_call is the function body you're constructing, which is itself just
>>> a
>>> one liner which calls the symbol FUN with the appropriate substitutions.
>>
>>
>> Yup. ?With a bit more infrastructure you could probably modify it so
>> that multiple curries collapsed into the equivalent single curry.
>>
> Yes I could see how one would do that - if the match.call detects a Curry as
> the first function being called, we would short circuit the usual evaluation
> into a different path which properly collapses all the nesting.
>
> It's interesting how R offers these facilities to override the usual
> evaluation order, but if one does that too much it could easily become
> confusing. I was looking at Rpipe the other day
> (https://github.com/slycoder/Rpipe) and the way he implements it is by
> defining his own Eval.
>

The proto package does currying on proto methods by defining $.proto
appropriately:

library(proto)
p <- proto(a = 1, b = 2)

# same as ls(p) - output is c("a", "b")
p$ls()

Here ls() is _not_ a special proto method but is just the ordinary
ls() provided by R.  $.proto calls ls() sticking in p as the first
argument.  A proto object is an environment and ls with a first
argument that is an environment lists the names of the objects in that
environment.  Similarly:

p$as.list()
p$str()
p$parent.env()
p$print()
p$eapply(length)

are the same as as.list(p), str(p), parent.env(p), print(p) and
eapply(p, length).

Although this might seem like its just syntax in proto it does allow
one to override the method.  For example,

p2 <- proto(a = 1, b = 2, print = function(.) with(., cat("a:", a,
"b:", b, "\n")) )

p2$print() # uses p2's print

print(p2) # uses R's print

etc.

-- 
Statistics & Software Consulting
GKX Group, GKX Associates Inc.
tel: 1-877-GKX-GROUP
email: ggrothendieck at gmail.com



[Rd] Curry: proposed new functional programming, er, function.
Gabor Grothendieck