CLOS isn't my strong point, but usually you call the methods using call-method, which tries to hide such details from you, however I think it can be done in non-portable ways. It may also be possible to make this doable in a portable way via the MOP. Maybe someone else more knowledgeable about CLOS here can answer, or maybe you should actually ask c.l.l and some MOP expert like Pascal Constanza could give you a proper answer.
>>10
I somehow doubt the Sussman cares a lot about CLOS.
If you dislike c.l.l, you can ask on IRC, I've found it quite helpful when asking various specific CL questions, however I think OP's question might be better fitted for newsgroups than IRC for a variety of reasons(complexity, expected answer length, poster's knowledge about the subject, ...).
Hmm, I guess I learn something new each day: define-method-combination name lambda-list (method-group-specifier*) [(:arguments . args-lambda-list)] [(:generic-function generic-function-symbol)] [[declaration* | documentation]] form*
Example usage: http://www.cawtech.demon.co.uk/clos/define-method-combination.html
I really ought to read a CLOS book these days, it seems rather neat.
Is this what you wanted OP?
Name:
Anonymous2010-02-09 10:39
Not quite. It turns out there's no way to get information on the current invocation because apparently caching effective methods is a big thing.