Re: A couple of problems with new module code.

Jerry> (1) the module autoconf stuff is completely independent Jerry> from the core XEmacs autoconf stuff, so it might as well Jerry> use the latest and greatest Wrong. Don't upgrade requirements to >= while something else (the core, yet!) requires <=. It's a massive pain in the ass, because some people won't have one or the other, and those who have both will make varying decisions about the default. If that file works with autoconf 2.13, just copy it to configure.in. Jerry> Here's a shot in the dark: is the cvs checkout procedure Jerry> automatically running autoconf for you on the module Jerry> configure.ac files? No. CVS doesn't do that, unless you make a wrapper script AFAIK. Jerry> If so, I can well imagine that there is top-level configure Jerry> or makefile magic that says, "run all configure scripts in Jerry> subdirectories". Running defaults is easy. But what happens when somebody adds options to one of the configure sub-scripts? How do they get passed? -- 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