Title Ordering autoloads [was: `defclass' and `defmethod' autoloads]
Type feature Module core code other
Severity inconvenience Platform N/A
Keywords Nosy List
These controls should only be changed by committers and tracker administrators.
Status deferred   Reason
Superseder   Submitted 2007-11-07.06:50:37
Priority normal   Assigned To

Created on 2008-01-19.04:58:03 by stephen, last changed 2008-01-23.10:53:49 by stephen.

msg86 [hidden] ([hidden]) Date: 2008-01-19.04:58:03
  Message-ID: <>
Michael Sperber writes:
 > "Stephen J. Turnbull" <> 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.

XEmacs-Patches mailing list
Date User Action Args
2008-01-23 10:53:49stephensetstatus: new -> deferred
severity: inconvenience
title: [R21.4R21.5] `defclass' and `defmethod' autoloads -> Ordering autoloads [was: `defclass' and `defmethod' autoloads]
module: + core code other
priority: normal
platform: + N/A
type: feature
2008-01-19 04:58:03stephencreate