Re: iterating over arguments

[Sam Steingold]

Eric Blake wrote:
> any rate, using 'autoconf --trace=_CL_CLISP_REQUIRE_FEATURE_2' would show
> what the result of m4_toupper turns out to be in this case.

running this:
autoconf --trace=CL_CLISP
hangs forever without any output.
(cvs with this patch:

Index: src/m4/clisp.m4
===================================================================
RCS file: /cvsroot/clisp/clisp/src/m4/clisp.m4,v
retrieving revision 1.13
diff -u -w -p -F^(def -r1.13 clisp.m4
--- src/m4/clisp.m4     13 Sep 2009 05:18:19 -0000      1.13
+++ src/m4/clisp.m4     14 Sep 2009 15:28:22 -0000
@@ -66,6 +66,8 @@ if test "$cl_use_clisp" != "no"; then
   fi
 fi
 m4_foreach_w([cl_feat], [$1],
-[AC_CACHE_CHECK([for cl_feat in CLISP], [cl_cv_clisp_]cl_feat,
+[m4_pushdef([CL_FEAT], [m4_toupper([cl_feat])])dnl
+AC_CACHE_CHECK([for CL_FEAT in CLISP], [cl_cv_clisp_]cl_feat,
  [CLISP_SET([cl_cv_clisp_]cl_feat,[[#+]]cl_feat[[ "yes" #-]]cl_feat[[ "no"]])])
-test $cl_cv_clisp_]cl_feat[ = no && AC_MSG_ERROR([no ]cl_feat[ in CLISP])])])
+test $cl_cv_clisp_]cl_feat[ = no && AC_MSG_ERROR([no ]cl_feat[ in CLISP])
+m4_popdef([CL_FEAT])])])

)