[closer-devel] ACL 8.0 generic-function-argument-precedence-order

[Pascal Costanza]

On 14 Sep 2007, at 05:02, Vyacheslav Akhmechet wrote:

> Hi,
>
>> From what I understand from MOP recommendation
> generic-function-argument-precedence-order is meant to return only
> required arguments. Quoting the recommendation, "This value is a list
> of symbols, a permutation of the required parameters in the lambda
> list of the generic function." So far I've verified that this is
> honored in SBCL and LispWorks, but not ACL:
>
> (defmethod foo (a b c &rest d) nil)
> (generic-function-lambda-list #'foo)
> => (A B C &REST D)
>
> Am I misunderstanding the spec? Are there plans to fix this?

I haven't been aware of this incompatibility yet. It should be  
straightforward to provide a workaround in Closer to MOP, so I will  
look into this.


Pascal

> [1] http://www.podval.org/~sds/clisp/impnotes/mop-gf.html#gf- 
> argument-precedence-order
> _______________________________________________
> closer-devel mailing list
> closer-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/closer-devel

-- 
Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net
Vrije Universiteit Brussel, Programming Technology Lab
Pleinlaan 2, B-1050 Brussel, Belgium