Re: A couple of problems with new module code.

Jerry> Steve Youngs <youngs(a)xemacs.org&gt; wrote: This is what _should_ happen. The autoloads should be there, and they should generate an informative error message if the .ell isn't present. Any modules that are distributed with XEmacs should be considered standard (eg, md5, gzip). If these aren't there, then it's like not having XPM "this loser platform is gonna lose, OK? if you don't like that, install $MODULE_SRC". 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. Jerry> On the other hand, this doesn't support installing new Jerry> modules later on that did not exist when the XEmacs binary Jerry> was compiled. On the gripping hand, that would still be a Jerry> problem if auto-autoloads.el contained only autoloads for Jerry> modules installed at build time. That's right. 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. :-) -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py