Re: AU_DEFUN obsolete functions

>>>>> "adl" == Alexandre Duret-Lutz <duret_g@xxxxxxxxxxxxx> writes:

adl> This is a patch that we can't apply before some work is done in
adl> Autoconf.  I'm sending it in before I lose it, and in case
adl> someone else wanted to work in this area.

adl> Basically there are two issues, one of which is already solved.

adl> 1. Autoconf 2.53 does not honor AU_DEFUN from aclocal.m4.  The
adl> current CVS version does, so we can wait for the next release and
adl> depend on this one.  (I believe there will be other reasons to
adl> depend on a greater Autoconf version.)

I fail to understand in what way this prevents you from installing the
patch.  AFAICS, it will work for both, but better with 2.54.

adl> 2. Some AU_DEFUNs in Autoconf substitute calls to AC_REQUIRE,
adl> which is not supported at the top-level.  This causes the last
adl> $AUTOCONF call of obsolete.test (the new version from this patch)
adl> to fail.

That's why I recommend removing all the AC_REQUIRE you have in these
macros.  AC_REQUIRE is forbidden in AU_DEFUN.

Also, you might want to use AU_ALIAS:

| # AU_ALIAS(OLD-NAME, NEW-NAME)
| # ----------------------------
| # The OLD-NAME is no longer used, just use NEW-NAME instead.  There is
| # little difference with using AU_DEFUN but the fact there is little
| # interest in running the test suite on both OLD-NAME and NEW-NAME.
| # This macro makes it possible to distinguish such cases.
| #
| # Do not use `defn' since then autoupdate would replace an old macro
| # call with the new macro body instead of the new macro call.
| m4_define([AU_ALIAS],
| [AU_DEFUN([$1], [$2($][@)])])


Hm...  Btw, maybe you would want to use Autoconf's test suite
framework to test _your_ macros?