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

[codesite-noreply at google.com]

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

Hmm... Sorry, Paolo, I don't follow your argument... you seem to make some  
assumptions that aren't explicitly
stated. Are you basing this on an existing implementation of MessageSend  
somewhere other than Squeak?

Why is it not a message send if the arguments are not yet all specified? A  
MessageSend (at least in Squeak and
as it is used in Seaside) represents a *future* message send. The message  
can't actually be sent until all the
parameters are specified but there's no reason they all have to be  
specified when the object is created.

And yes, it is polymorphic with a block - so is the existing MessageSend in  
Squeak (at least in theory). From
the class comment:

"Instances of MessageSend encapsulate message sends to objects. Arguments  
can be either predefined or
supplied when the message send is performed.

Use #value to perform a message send with its predefined arguments and  
#valueWithArguments: if additonal
arguments have to supplied."

The idea of MessageSend (again, at least as used in Seaside) is to optimize  
by replacing block contexts when
all the block does is call a method with the parameters of the block.  
Callback has a very specific meaning in
Seaside and this class is more general than that.


--
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