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

codesite-noreply at google.com codesite-noreply at google.com
Sat Jan 3 10:58:20 UTC 2009


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

Well, in my opinion, #numArgs on WAMessageSend should return the number of  
free arguments. If an argument
is already bound you shouldn't be able to change it with a #value* method.

Alternatively, I suppose you could implement #freeArgs (preferably  
#freeArguments actually - I hate
abbreviations in method names) on WAMessageSend and BlockContext and use  
that but I don't see why that
should be necessary.

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


More information about the seaside-dev mailing list