are also suggestions we should either satisfy right now (they're
easy), or remove (obsoleted since then).
-** AC_PROG_GNU_M4
-Document.
+** tests/
+Write the sketch of a new series of tests, written in Autotest,
+cf. recode 3.5 by François Pinard. It has to be shell scripts so that
+everybody can run it, and most people can read it. Not like DejaGNU.
-** Produce a static list of all the AC_SUBST.
-This would greatly help Automake and the independence of Automake and
-Autoconf. Currently Automake needs inner details of Autoconf.
+It is important to start before the release, even if the test suite is
+ridiculously small, so that people see a framework in which they may
+provide their additional tests.
+
+** testsuite/config/unix.exp
+Fix the regex snippet so that it properly parses the current version
+of Autoconf.
+
+** AC_ARG_VAR
+If should check that none of the envvar it is in charge of, has
+changed. The configure.in writer may supply what to do (FATAL, WARN
+etc.). See VALIDATE CACHE TUPLE.
** autoconf.texi: config.status in node names.
The info mode of Emacs seems to have problems with this. The info
reader catches this properly, so we should report to the X?Emacs teams.
Bug triggered by looking for `CONFIG_FILES' in the index.
-** AC_CONFIG_FILES, AC_CONFIG_COMMANDS.
+** AC_CONFIG_FILES, AC_CONFIG_COMMANDS, AC_CONFIG_HEADERS, AC_CONFIG_LINKS.
Will we need both ICMD and CMD as is the case for AC_OUTPUT_COMMANDS?
If so, they have to be adapted.
to have all the AC_CONFIG_ together, but it is not currently the
case. An architecture for the docs needs to be decided.
+** autoconf.texi: Document the extensions of AC_CONFIG_*
+The fact we can run commands.
+
** AC_CONFIG_PRE_COMMANDS, AC_CONFIG_POST_COMMANDS.
We still have to discuss a few issues: should the pre-commands be run
before the cache is created? Are the names OK? Document, see above.
So that --recheck does not pass --no-recursive to configure.
** Allow --header, --command, --file to config.status.
-I don't remember the purpose, ask Alexandre.
+./config.status --file foo, would work on foo as if it were a config
+file. It would be great that we could use stdin and stdout also.
** Move AM_PROG_CC_STDC into Autoconf.
Autoconf should provide the means to determine the ANSIsm of the
I've done it, but this is the last opportunity to change this macro
name: AC_PROG_CC_ISO? Or even more specific for the ISO version?
-** Provide means to provides commands to run before AC_OUTPUT.
-This is what is needed for LTLIBOBJS and others.
-
** Document GNATS?
-** fnmatch
-From: Stanislav Brabec <utx@k332.feld.cvut.cz>
-
-If AC_LANG is c++ and c++ is (at least) gcc-2.95.1, the result is error;
-it can be fixed on my system by #include <fnmatch.h>, but I don't
-know, if it is general include.
-Other possible fix is checking for fnmatch using cc in any case.
-
-
-Log part:
-
-configure:1955: checking for working fnmatch
-configure:1973: c++ -o conftest -O69 -fomit-frame-pointer -I/usr/games/include -I/usr/games/include confte
-st.C -lclanlayer2 -lclan -L/usr/X11R6/lib -L/usr/games/lib 1>&5
-configure: In function `int main()':
-configure:1970: implicit declaration of function `int fnmatch(...)'
-configure: failed program was:
-#line 1966 "configure"
-#include "confdefs.h"
-#ifdef __cplusplus
-extern "C" void exit(int);
-#endif
-main() { exit (fnmatch ("a*", "abc", 0) != 0); }
-
-
** We should remove obsolete things.
Both in the doc and the code. Looking for the keyword `obsolete'
proves to be useful.
acfunc.m4. I suppose there should be small exceptions, e.g., the
family AC_REPLACE_FUNCS should still be in acfunc.m4.
+** Cache name spaces.
+Cf the discussion with Kaveh. One would like to
+AC_CHECK_FUNCS(bar)
+# Do something that changes the environment
+AC_CACHE_PUSH(foo)
+AC_CHECK_FUNCS(bar)
+AC_CACHE_POP
+in order not to erase the results of a check with another.
+
+** Cache var names
+should depend upon the current language.
+
** Use m4 lists?
I think one sad decision in Autoconf was to use white space separated
lists for some arguments. For instance AC_CHECK_FUNCS(foo bar). I