Frank, yes I have, but I wasn't quite happy with the protocol used nor the creation of CurriedBlock and Currier classes. My idea is to create a new method #curry: in BlockClosure, which in turn, returns another BlockClosure (with n-1 arity). Thanks again. 2012/12/26 Frank Shearar <frank.shearar@gmail.com>
On 26 December 2012 00:54, Sebastián Krynski <skrynski@gmail.com> wrote:
Esteban, thanks for your answer.. I think i need to dynamically create a block which accepts exactly n parameters , so that the new block would behave as expected. Is that possible ? Is that what you had in mind?
You have read Vassili Bykov's posts on the subject, right? Starting here: http://blog.3plus4.org/2007/03/23/currying-in-smalltalk/
frank
2012/12/25 Esteban A. Maringolo <emaringolo@gmail.com>
You can use #valueWithArguments: or #valueWithPossibleArgs: instead of using #value:value:value:
numArgs instVar might be your friend in what you want to achieve.
Regards,
-- View this message in context: http://forum.world.st/on-blockclosure-currying-tp4660895p4660896.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.