[R21.4R21.5] `defclass' and `defmethod' autoloads

[Stephen J. Turnbull]

Michael Sperber writes:
 > 
 > "Stephen J. Turnbull" <stephen at xemacs.org> writes:
 > 
 > > Michael Sperber writes:
 > >
 > >  > The question is how do you get it there?  And in such a way that it's
 > >  > guaranteed to be there before it gets used.
 > >
 > > I was thinking auto-autoloads.  If the relevant package isn't there,
 > > then you're gonna be hosed anyway.
 > 
 > The problem is there's no direct control over the order in which
 > auto-autoloads are loaded.  (Or did I miss something.)

I didn't see anything that immediately looked order-dependent in
*autoloads*, it's more likely I missed something.  Maybe this is
something we should revisit for 23.0.