Re: Treatise on require

[Andreas Schwab]

Bill Wohler <address@hidden> writes:

> Over time, nasty circular dependencies have reared their ugly head in
> MH-E. For example, mh-e requires just about other file and just about
> every other file requires mh-e. Just for fun there are mini-loops with
> mh-customize and and mh-utils. This is currently handled by putting the
> call to provides (in mh-e.el) before the various calls to require (whose
> files require mh-e).

IMHO in the long run it would be better to reorganize the files to remove
the circular dependencies.  For example the interdependency between
mh-customize and mh-utils appears to be gratuitous judging just from the
file names.  Maybe the common functions should be factored out to
different/new file.

Btw, looking at mh-utils.el, I don't think it should use `load' for
optional dependencies.  The libraries may already be loaded and should not
be reloaded just by loading mh-utils.  For example, tool-bar is already
preloaded in most configurations.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."