[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
method combinations changing
- To: Patrick Dussud <dussud@lucid.com>
- Subject: method combinations changing
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Fri, 19 Jan 90 13:52 EST
- Cc: common-lisp-object-system@sail.stanford.edu
- In-reply-to: <9001191812.AA04630@challenger>
Date: Fri, 19 Jan 90 10:12:17 PST
From: Patrick Dussud <dussud@lucid.com>
Since method combination are very close to macros, could be adopt the same
language about caching and calling?
No, for the obvious reason that one can look at a program and point to
all the places where a macro is called, but one cannot find in the source
text of a program the places where a method combination type is called.
It happens inside of generic-function dispatch somewhere, and its arguments
come from method definitions scattered all over the program, not from a
single form at a single location in the source. Thus what ANSI CL says about
when macros must be expanded cannot be reworded to apply to method combination.