This page is part of the web mail archives of SRFI 26 from before July 7th, 2015. The new archives for SRFI 26 contain all messages, not just those from before July 7th, 2015.
On Tue, Feb 12, 2002 at 08:17:19AM -0600, John David Stone wrote: > Sebastian Egner writes: > > Would 'partial-apply' be fine with you? > > Well, it would be better than CURRY. On the other hand, I think > it's a potential source of confusion, since the interface to your macro is > different from that of APPLY, which requires its last argument to be a > list. > > In my work, I've used the name CALL for the following procedure, > which is like APPLY except that the arguments are provided severally > instead of being bundled into a list: > > (define call > (lambda (procedure . arguments) > (apply procedure arguments))) > > I think of your macro as ``partial CALL'' rather than ``partial APPLY.'' Another option would be to call it "specialise", since it specialises a function. After all, the function isn't called/applied/invoked at all by the call to TFWAN. [1] Stephan [1] TFWAN == The Form Without A Name, of course