[Seaside-dev] Issue 268 in seaside: Introduce WAMessageSend

[codesite-noreply at google.com]

Comment #8 on issue 268 by renggli: Introduce WAMessageSend
http://code.google.com/p/seaside/issues/detail?id=268

> It sounds like there is agreement that Seaside should have a class that  
holds a receiver and a selector, and
supports optionally currying some or all of the arguments. #numArgs should  
therefore return the number of free
arguments and the #value* methods should operate on that basis as well.

Yes, this is what we need.

Are remaining arguments always appended to the end? Or can they be  
introduced at specific positions in any
order? Is the receiver treated the same way as an argument? For example  
would it be possible to represent the
following block as a "message send" object?

    [ :x :y | y foo: a1 bar: a2 zork: x ]
    (x, y are free vars; a1, a2 are bound vars; #foo:bar:zork: is the  
selector)

I think being able to support that would be quite useful in the context of  
Seaside. How would such an object be
specified?

It looks a bit like a generalization of Vassili Bykov's "Selectors as  
Blocks", see http://blog.3plus4.org/2007/03/27/selectors-as-blocks/ and the  
following posts.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings