Re: AC_REQUIRE problems

[Stepan Kasal]

Hi,

> > AC_IF(TEST, THEN-CODE, [ELSE-CODE])

interestingly enough, we already have an AS_IF macro in m4sh.m4.

But it's defined by m4_define, not m4_defun.  This simple change would
bring the change that m4_required (i.e. AC_REQUIREd) macros would go
_before the if_ as soon as AS_IF is used.

I have just verified that the patch patch below doesn't break autoconf's
make check.

Paul, OK to commit this?

Stepan

2005-02-12  Stepan Kasal  <address@hidden>

        * lib/m4sugar/m4sh.m4 (AS_IF): Define by m4_defun, not m4_define.
        This causes that any required macros inside will get before the if.

Index: lib/m4sugar/m4sh.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/m4sugar/m4sh.m4,v
retrieving revision 1.135
diff -u -r1.135 m4sh.m4
--- lib/m4sugar/m4sh.m4 5 Feb 2005 07:58:43 -0000       1.135
+++ lib/m4sugar/m4sh.m4 12 Feb 2005 10:19:37 -0000
@@ -448,7 +448,7 @@
 # with simplifications is IF-TRUE and/or IF-FALSE is empty.
 #
 # FIXME: Be n-ary, just as m4_if.
-m4_define([AS_IF],
+m4_defun([AS_IF],
 [m4_ifval([$2$3],
 [if $1; then
   m4_ifval([$2], [$2], :)