[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Method-lambda and apply-method-lambda
- To: Patrick H Dussud <DUSSUD@Jenner.csc.ti.com>
- Subject: Re: Method-lambda and apply-method-lambda
- From: kempf@Sun.COM
- Date: Fri, 25 Mar 88 13:43:43 -0800
- Cc: Common-lisp-object-system@sail.stanford.edu
- In-reply-to: Your message of Fri, 25 Mar 88 14:38:09 -0600. <2784314289-5590063@Jenner>
>>I don't think that method-lambda, as describe in 88-003 is good enough. It
>>captures the contract between a class of generic functions and a class of methods,
>>so it should be metaclass driven. You can imagine several contracts on a single
>>implementation.
Why, precisely, do you think there need be any difference between a method
function and any other kind of function? I can understand this for
a generic function, since a generic function has slots, but a method
function has none. It seems to me that most of how a method function
differs is covered by additions to its lexical environment, and that
FUNCALL and APPLY should do.
jak