Re: A couple of problems with new module code.
"Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
[snip]
Ie, this
Jerry> (when (file-exists-p "module.ell")
should be
(if (not (file-exists-p "module.ell"))
(error 'file-error
"module.ell doesn't exist. Probably you haven't built
it.")
(dl-load "module.ell")
(module-do-stuff))
The fact that today's sources include clearly optional stuff like
postgresql and ldap should be considered transitional, not
(necessarily) a design flaw in Jerry's code IMO.
Right. So, as you say below, what we really want are required modules,
which are distributed with the core (or maybe as part of xemacs-base or
something like it) and use code like your above, and optional modules
that are distributed as packages with self-contained autoloads.
What should be happening in the long run is that the modules get
moved
into packages. Then there's no problem, except the technical one of
building modules as packages. But Jerry's real smart, the rest of us
needn't worry. :-)
Hmmmm. Mind if *I* worry? I have been thinking about this idly now and
then. Maybe I'll think about it seriously while on an extended trip at
the end of this month....
--
Jerry James, who has lost every chess game he's ever played
http://www.ittc.ku.edu/~james/