🚀 go-pugleaf

    From: Barry Margolin <barmar@Think.COM>
    Subject: Re: no-applicable-method
    To: tk@research.att.com
    Cc: mh5l+@andrew.cmu.edu, comp.lang.clos@cis.ohio-state.edu
    In-Reply-To: <19920416170513.9.TK@PETZL.research.att.com>
    Message-Id: <19920416182843.6.BARMAR@occam.think.com>

	Date: Thu, 16 Apr 1992 13:05 EDT
	From: Thomas Kirk <tk@HUNNY.research.att.com>

	    From: barmar@think.com (Barry Margolin)

	    However, this won't work if you're trying to do this to generic functions
	    that you don't define yourself, since you can't override their metaclasses.

	this will work fine. assuming that you can get at the generic functions,
	just change the class of the generic function object, like so:

    Sorry, this isn't permitted.  According to p.197 of "The Art of the
    Metaobject Protocol", third paragraph, "the class of a generic function
    metaobject may not be changed...".

						    barmar

true enough. however, given that (a) this is a useful thing to do,
and (b) many extant CLOS implementations allow it, it may be worthwhile 
to relax this restriction. it's in the spirit of the specification in 
the AMOP to consider such improvements, unless there's some convincing 
rationale for leaving it alone (perhaps there is, but i can think of 
no reason myself).