Bruno Haible <bruno@...> writes:
> The MOP doesn't support change-class on a generic-function. However, SBCL
> apparently supports it, since it doesn't give an error or warning when
> I do so. Then, however, it produces wrong results for calls to this
> generic function.
Thanks. I've "fixed" this for now by disallowing CHANGE-CLASS of
metaobjects in line with AMOP; while it would be relatively simple to
allow generic functions to be changed (by flushing all the caches in
update-instance-for-redefined-class...) I'm not wild about the idea,
so I'll leave that implementation to someone who needs it.